CVE-2026-89141: AI Engine (WordPress plugin) · Insecure Direct Object Reference
Affects AI Engine (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| tigroumeowAI Engine – The Chatbot, AI Framework & MCP for WordPress | Affected
| Fixed in– |
AI-suggested
Users should disable the Public API module in the plugin settings to prevent access to the vulnerable REST endpoint, as this disables the attack vector. Monitor the vendor advisory for updates regarding an official fix or patch.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/2cb2ad5d-aa92-4186-aaae-45dde4a52f30?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.7.7/classes/api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.7.7/classes/api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.7.7/classes/core.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.7.7/classes/api.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3693379 (opens in a new tab)