CVE-2025-11749

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

2025-11-04 17:19
Emiliano Versini

Strategic Overview

Status
Patched in 3.1.4
Affected Plugin
AI Engine – The Chatbot, AI Framework & MCP for WordPress
Affected Version
<= 3.1.3
CVSS
9.8Critical
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-11749
View all AI Engine – The Chatbot, AI Framework & MCP for WordPress vulnerabilities

At a glance

CVE-2025-11749 is a critical-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the AI Engine WordPress plugin, affecting versions <= 3.1.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.1.4; sites on affected versions should update now. Disclosed November 2025, reported by Emiliano Versini.

Vulnerability Overview

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.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in AI Engine <= 3.1.3 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For AI Engine the fix is 3.1.4: builds <= 3.1.3 are affected, anything from 3.1.4 onward is not.

Remediation

Update to version 3.1.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: AI Engine 3.1.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-11749https://www.wordfence.com/threat-intel/vulnerabilities/id/06eaf624-aedf-453d-8457-d03a572fac0dhttps://nvd.nist.gov/vuln/detail/CVE-2025-11749

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C