AI Engine <= 3.7.7 - Insecure Direct Object Reference to Authenticated (Subscriber+) Sensitive Attachment Disclosure via 'mediaId' Parameter
Strategic Overview
- Status
- Patched in 3.7.8
- Affected Plugin
- AI Engine – The Chatbot, AI Framework & MCP for WordPress
- Affected Version
<= 3.7.7- CVSS
- 6.5Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-89141
At a glance
CVE-2026-89141 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the AI Engine WordPress plugin, affecting versions <= 3.7.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.7.8; sites on affected versions should update now. Disclosed September 2026, reported by Chi Trung Huynh.
Vulnerability Overview
The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.7.7 via the 'mediaId' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to access and retrieve the transcribed contents of private audio attachments belonging to other users, including Administrators, via a supplied attachment ID. This vulnerability requires the Public API module to be enabled in the plugin settings; when disabled, the REST route is absent and the endpoint returns HTTP 404.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-639: Authorization Bypass Through User-Controlled Key
AI Engine <= 3.7.7 carries this weakness at mediaId, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For AI Engine the fix is 3.7.8: builds <= 3.7.7 are affected, anything from 3.7.8 onward is not.
Remediation
Update to version 3.7.8, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: AI Engine 3.7.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in AI Engine – The Chatbot, AI Framework & MCP for WordPress
- 9.8CVE-2025-11749: AI Engine Info Exposure to Privilege Escalation
CVE-2025-11749 - 9.8CVE-2023-51409: AI Engine: ChatGPT Chatbot Arbitrary File Upload
CVE-2023-51409 - 9.1CVE-2024-34440: AI Engine: ChatGPT Chatbot Arbitrary File Upload
CVE-2024-34440 - 8.8CVE-2026-15988: AI Engine <= 3.6.5 CSRF to Privilege Escalation
CVE-2026-15988 - 8.8CVE-2026-8719: AI Engine 3.4.9 Privilege Escalation
CVE-2026-8719 - 8.8CVE-2025-7847: AI Engine 2.9.3 - 2.9.4 Arbitrary File Upload
CVE-2025-7847 - 8.8CVE-2025-5071: AI Engine 2.8.0 - 2.8.3 Insufficient Authorization
CVE-2025-5071 - 8.0CVE-2025-6238: AI Engine 2.8.4 Insecure OAuth Implementation
CVE-2025-6238
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C