HomeWordPress vulnerabilitiesOptima Express IDX
Optima Express IDX vulnerabilities
Optima Express IDX has 3 known vulnerabilities in this database. The most recent published record is dated 27 Sep 2026.
- Known vulnerabilities
- 3
- Active installs
- 10,000+
- Latest version
- 8.7.7
- Last updated
- 23 Sep 2026
- Most recent
- 27 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-96899 | Medium 6.8 | Before 8.7.6 | Fixed in 8.7.6 | 10 d ago |
| Broken access control CVE-2026-96897 | Medium 5.3 | Before 8.7.6 | Fixed in 8.7.6 | 10 d ago |
| Privilege escalation CVE-2026-93901 | High 7.3 | Up to 8.7.5 | Fixed in a later version (latest 8.7.7) | 12 d ago |
Read the published descriptions
- CVE-2026-96899, 27 Sep 2026
- The Optima Express IDX WordPress plugin before 8.7.6 does not properly neutralise a script value submitted through one of its REST endpoints before storing it and echoing it into the document head when the post is rendered, allowing users with a role as low as author to perform Stored Cross-Site Scripting attacks. CVE record
- CVE-2026-96897, 27 Sep 2026
- The Optima Express IDX WordPress plugin before 8.7.6 does not perform any authorisation check on one of its AJAX actions that is available to logged-out users, allowing unauthenticated attackers to force the creation of a fixed author-role account and to repeatedly rotate its application password on any connected install. CVE record
- CVE-2026-93901, 25 Sep 2026
- 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. CVE record
What to do if you run Optima Express IDX
If you run Optima Express IDX, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Optima Express IDX vulnerabilities
Free. We email you when a new vulnerability is published for Optima Express IDX, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.