OCTOBER 9, 2026
Live Feed
Back to database
Case File

CVE-2026-93901

HIGH · CVSS 7.3 EPSS 0.35% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-25 · Last synced 2026-10-09

CyberRota Analysis

AI-Generated

The Optima Express IDX plugin for WordPress is vulnerable to privilege escalation due to a flaw in the `provisionBlogCredentials()` function, which can be accessed without proper authentication or capability checks. This allows unauthenticated attackers to escalate a pre-registered `optima-express` account to the Author role, granting them significant permissions such as publishing posts and accessing sensitive REST endpoints. WordPress site administrators using this plugin should prioritize patching this vulnerability, especially if open user registration is enabled.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-93901
Severity
HIGH
CVSS
7.3
EPSS
0.35%
WordPress

Original NVD 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.