CVE-2025-11749: AI Engine (WordPress plugin) · Information Exposure
Affects AI Engine (WordPress plugin)Source CVE Database V5
Not known to be exploited · public exploit available (Metasploit) · 74% EPSS · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 74.6% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2025
Detectable: evidence found.
nuclei template: WordPress AI Engine Plugin - Token Exposure
Weaponised: evidence found.
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| tigroumeow AI Engine – The Chatbot, AI Framework & MCP for WordPress | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, it is recommended to disable the 'No-Auth URL' feature to prevent exposure of the Bearer Token. Monitor vendor communications closely for updates and apply patches promptly once available.
Description
The AI Engine plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.3 via the /mcp/v1/ REST API endpoint that exposes the 'Bearer Token' value when 'No-Auth URL' is enabled. This makes it possible for unauthenticated attackers to extract the bearer token, which can be used to gain access to a valid session and perform many actions like creating a new administrator account, leading to privilege escalation.