ZeroHour

CVE-2025-11749

large

Sensitive Information Exposure in WordPress AI Engine Plugin (Bearer Token Leak)

CVSS 3.1
9.8 critical
EPSS
75%p99
Published
()
Modified
AI analysis

The AI Engine plugin for WordPress, in all versions up to and including 3.1.3, exposes its 'Bearer Token' value via the /mcp/v1/ REST API endpoint whenever the 'No-Auth URL' option is enabled (CWE-200). Because the endpoint is unauthenticated, any remote attacker can query it and read the bearer token directly from the response. With that token, the attacker can gain access to a valid authenticated session and perform many actions on the site, including creating a new administrator account, leading to full privilege escalation. Any WordPress site running AI Engine 3.1.3 or earlier with 'No-Auth URL' enabled is affected. No public proof-of-concept is known and the flaw is not yet in CISA KEV, but the very high EPSS score of 74.8% (99th percentile) indicates a strong likelihood of exploitation within 30 days.

What to do: Update the AI Engine plugin to a patched release newer than 3.1.3 as soon as possible. Until patched, disable the 'No-Auth URL' option or restrict access to the /mcp/v1/ endpoint (e.g., via WAF/rewrite rules), rotate the exposed bearer token, and review the site for any administrator accounts created without authorization.

Affected
Meow Apps AI Engine (WordPress plugin)all versions up to and including 3.1.3
Estimated exposure
large≈100,000+ WordPress sites (plugin's public active-install count; exposed subset limited to sites with 'No-Auth URL' enabled) — AI Engine lists roughly 100,000 active installations on wordpress.org, and only the subset of those with the 'No-Auth URL' option enabled actually exposes the token-bearing /mcp/v1/ endpoint, so real-world exposure is likely somewhat lower…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

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.

Ecosystems
WordPress
Weakness
CWE-200
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

In the news

No ingested article mentions this CVE yet.