AI Engine EUVD-2026-53726

Exploitation requires a valid WordPress user account with at minimum the Editor role - unauthenticated remote attackers cannot exploit this vulnerability. The AI Engine plugin must be installed, active, and configured with at least one third-party API key or authentication token stored in the database; installations with no stored secrets expose nothing of value. The attacker must be able to reach the specific admin page where AI Engine renders its inline configuration script (standard WordPress admin panel network access). Exploitation is bounded by: (1) requiring authenticated Editor or higher access, which limits the attacker pool to insiders or accounts obtained through separate compromise; (2) the target site must have AI Engine actively configured with credentials; (3) the attack is not automatable per SSVC due to the authentication requirement.

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) scores 6.5 (Medium), accurately reflecting network-accessible exploitation requiring only Editor-level credentials with no additional complexity. However, the EPSS score of 0.17% at the 7th percentile indicates very low real-world exploitation probability despite the public POC, suggesting opportunistic exploitation has not yet materialized at scale. SSVC assessment corroborates this: exploitation status is POC-only, the attack is not automatable (requires authenticated access with a specific role), and technical impact is partial. The actual business risk is disproportionate to the CVSS score in environments that store high-value credentials (e.g., paid OpenAI API keys): a compromised API key can result in financial abuse, unauthorized data access through the AI service, or lateral pivot if the same credentials are reused. Sites where no API keys are configured expose no sensitive data. Not currently in CISA KEV.

An attacker with a legitimate WordPress Editor account - obtained via credential compromise, insider access, or social engineering - logs into the admin panel and navigates to the AI Engine configuration page. Without any special tooling, they view the page source or browser developer tools to locate the inline JavaScript block containing the plugin's configuration, where API keys and authentication tokens appear in cleartext. A public POC demonstrating this technique is available via WPScan, lowering the skill bar for exploitation.