What is the CVSS score of CVE-2025-11749?

CVE-2025-11749 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 85.9%.

Which versions of PHP are affected by CVE-2025-11749?

Organizations using for WordPress is vulnerable to Sensitive Information Exposure in all face critical risk from CVE-2025-11749, a information exposure vulnerability rated CVSS 9.8.

Is there a public PoC exploit available for CVE-2025-11749?

Yes, a public proof-of-concept exploit is available for CVE-2025-11749. Prioritise patching immediately. EPSS: 85.9%.

How to fix or mitigate CVE-2025-11749?

Within 24 hours: Identify all affected systems running for WordPress is vulnerable to Sensitive Information Exposur and apply vendor patches immediately. Monitor vendor channels for patch availability.

PHP CVE-2025-11749

CRITICAL

Information Exposure (CWE-200)

2025-11-05 security@wordfence.com

WordPress Information Disclosure Privilege Escalation PHP

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:20 vuln.today

CVE Published

Nov 05, 2025 - 06:15 nvd

CRITICAL 9.8

DescriptionCVE.org

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.

AnalysisAI

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint when the No-Auth URL feature is enabled. Unauthenticated attackers can extract this token to gain full API access, compromising AI assistant configurations and potentially accessing connected LLM provider API keys.

Technical ContextAI

When the No-Auth URL feature is enabled, the /mcp/v1/ endpoint returns configuration data including the Bearer Token in cleartext. This token is used to authenticate API requests to the AI Engine's chatbot and content generation features. The exposed token may also provide access to configured OpenAI/Anthropic API keys stored in the plugin settings.

Affected ProductsAI

AI Engine for WordPress <= 3.1.3

RemediationAI

Update AI Engine to version 3.1.4 or later. Disable the No-Auth URL feature if not required. Rotate all API keys for connected LLM providers. Review conversation logs for sensitive data exposure. Implement rate limiting on the MCP endpoint.