CVE-2026-89141: 
WordPress vulnerability analysis and mitigation

CVE-2026-89141 is an Insecure Direct Object Reference (IDOR) vulnerability in the "AI Engine – The Chatbot, AI Framework & MCP for WordPress" plugin for WordPress. It affects all versions up to and including 3.7.7, allowing authenticated attackers with subscriber-level access or above to access transcribed contents of private audio attachments belonging to other users, including Administrators. The vulnerability was published on September 15, 2026, and carries a CVSS v3.1 base score of 6.5 (Medium) (Feedly).

The vulnerability is classified as CWE-639 (Authorization Bypass Through User-Controlled Key). The plugin fails to validate whether the requesting user is authorized to access the resource identified by the mediaId parameter in a REST API endpoint. An authenticated attacker can supply an arbitrary attachment ID to retrieve transcribed audio content belonging to other users. Exploitation requires the "Public API" module to be enabled in the plugin settings; if disabled, the REST route is absent and the endpoint returns HTTP 404 (Feedly).

Successful exploitation results in unauthorized disclosure of private audio attachment transcriptions, including those belonging to Administrator accounts, representing a high confidentiality impact. There is no integrity or availability impact. The scope is limited to the affected WordPress instance, but sensitive information exposed through transcribed audio (e.g., meeting recordings, voice notes) could facilitate further attacks or privacy violations (Feedly).

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the publication date. The vulnerability requires authenticated access (subscriber-level or above), which lowers the risk compared to unauthenticated flaws, but subscriber accounts are commonly available on WordPress sites with open registration. The CVE status is listed as "Received" with no CISA KEV catalog entry or known EPSS score published at this time (Feedly).

1. Reconnaissance: Identify WordPress sites running the "AI Engine" plugin (version ≤ 3.7.7) with the Public API module enabled, using tools like WPScan or by checking plugin metadata at /wp-content/plugins/ai-engine/readme.txt.
2. Obtain authenticated access: Register or log in as a subscriber-level (or higher) user on the target WordPress site.
3. Enumerate attachment IDs: Use WordPress's REST API or other enumeration techniques to discover valid media attachment IDs (e.g., by iterating integer IDs).
4. Send crafted API request: Submit a GET or POST request to the vulnerable REST endpoint with the mediaId parameter set to the target attachment ID (e.g., GET /wp-json/ai-engine/v1/<endpoint>?mediaId=<target_id>).
5. Retrieve transcribed content: Parse the API response to obtain the transcribed text of the private audio attachment belonging to another user, including Administrators (Feedly).

• Network: Repeated REST API requests to the AI Engine plugin endpoint with varying mediaId parameter values from a single authenticated user session; sequential or random integer enumeration patterns in mediaId values.
• Logs: WordPress access logs showing authenticated low-privilege users (subscribers) making frequent requests to the AI Engine REST API route with different attachment IDs; HTTP 200 responses to requests for media IDs not owned by the requesting user.
• Application: Unexpected access to private audio attachment transcriptions by non-owner accounts visible in plugin or WordPress audit logs (if audit logging is enabled).

Users should update the "AI Engine – The Chatbot, AI Framework & MCP for WordPress" plugin to a version beyond 3.7.7 once a patched release is available from the vendor (tigroumeow). As an immediate workaround, administrators can disable the "Public API" module in the plugin settings, which removes the vulnerable REST route entirely and causes the endpoint to return HTTP 404. Additionally, restricting user registration on the WordPress site reduces the attack surface by limiting who can obtain subscriber-level access (Feedly).