CVE-2026-93901: Optima Express IDX (WordPress plugin) · Improper Privilege Management
Affects Optima Express IDX (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ihomefinderOptima Express IDX | Affected
| Fixed in– |
AI-suggested
Users should verify if a vendor advisory or update is available. Until then, mitigation includes disabling open user registration on the WordPress site to prevent attacker registration of the 'optima-express' username. Monitor for updates from the vendor and apply official patches once released.
Description
The Optima Express IDX plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 8.7.5. This is due to the `provisionBlogCredentials()` function in `iHomefinderAdmin.php` being reachable via the `wp_ajax_nopriv_ihf_clear_cache` AJAX action — through the call chain `iHomefinderAjaxHandler::clearCache()` → `activateAuthenticationToken()` → `getAuthenticationInfo()` → `provisionBlogCredentials()` — with no capability check, nonce verification, or ownership validation, and the function unconditionally calling `$user->set_role('author')` on whichever WordPress account matches the hard-coded login `optima-express` via `get_user_by('login', 'optima-express')`. This makes it possible for unauthenticated attackers to escalate a pre-registered `optima-express` account to the Author role, gaining `publish_posts`, `upload_files`, and `edit_published_posts` capabilities, including access to the plugin's own `/wp-json/optima-express/v1/blog-post` REST endpoint. Exploitation requires open user registration to be enabled on the target site, and the attacker must register the `optima-express` username before the plugin has had the opportunity to provision that login for its own integration account.
References
- wordfence.com/threat-intel/vulnerabilities/id/8ba63df6-ae71-4320-bb82-87d6e17cc47d?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinderAdmin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinderAdmin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinderAjaxHandler.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinder.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinderAdmin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinderAdmin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinder.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/optima-express/tags/8.7.5/iHomefinderAdmin.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3706448%40optima-express&new=3706448%40optima-express (opens in a new tab)