Skip to content
Fencer Vulns
critical 9.8

CVE-2025-11749 in the critical feed json

AI Engine <= 3.1.3 - Unauthenticated Sensitive Information Exposure to Privilege Escalation

published 2025-11-05 12 mo ago modified 2026-10-18 21 d ago also EUVD-2025-37802

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
74.8%
EPSS 74.8% chance of exploitation in 30 days, percentile 99.5%
public exploits
1
Metasploit, plus a Nuclei check

Summary

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.

Patch / fix

  • meowapps ai_engine 3.1.4

Timeline

  1. First public exploit (Metasploit exploit/multi/http/wp_ai_engine_mcp_rce)
  2. Published

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
12 mo ago

Exploit prediction

74.83% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • tigroumeow AI Engine – The Chatbot, AI Framework & MCP for WordPress

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.