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%.

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.

Wordpress Plugin CVE-2025-11749

Q: Which versions of Wordpress Plugin 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.

CRITICAL

Information Exposure (CWE-200)

2025-11-05 security@wordfence.com

WordPress Privilege Escalation Information Disclosure Wordpress Plugin

9.8

CVSS 3.1 · Vendor: wordfence

View

Vulnerability Assessment

Weakness	CWE CWE-200 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V14 - Data Protection Data exposure prevention MITRE ATT&CK 2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	CVSS 9.8, EPSS 85.9%. AI Engine is rapidly growing with increasing WordPress adoption of AI features. Exposed LLM API keys can be abused for unauthorized usage generating significant costs. The plugin may also store conversation histories containing sensitive user data.
Exploit ScenarioDerived	An attacker discovers a WordPress site with AI Engine installed. They access the /mcp/v1/ endpoint, which returns the Bearer Token. Using this token, they access the plugin's API to extract configured OpenAI API keys, download conversation logs containing user interactions, and modify the AI assistant's system prompt to inject malicious instructions.

Emergency Immediate action required. Why: CRITICAL + EPSS > 30%, no patch available.

No patch listed yet 85.9% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 28, 2026

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.

Earlier versions of this analysis (1)

v1 Mar 28, 2026 - 19:20 CVSS 9.8

Bearer token exposure in AI Engine WordPress plugin via unauthenticated MCP endpoint reveals API credentials for AI service integrations.

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.

Affected ProductsAI

AI Engine for WordPress <= 3.1.3

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

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.

Know when Wordpress Plugin gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (wordfence) PRIMARY 9.8 CRITICAL

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

Primary rating from Vendor (wordfence) · only source for this CVE.

CVSS VectorVendor: wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

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.

Executive ViewAI

Why It Matters

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. This could expose sensitive information including credentials, configuration data, or user records to unauthorized parties. With an EPSS score of 86%, this vulnerability faces very high likelihood of exploitation. Organizations should apply vendor updates immediately when available and implement compensating controls in the interim.

Business Impact: Severe

Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Restrict access to affected endpoints; (2) Implement additional authorization checks; (3) Enable audit logging.

Threat Intelligence Overview

Threat Score

6.0/10

Composite threat intelligence

EPSS Score

85.9%

Top 1% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS POC (2)

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 85.9%

Patch available No

Active threat Yes

Deciding rule

CRITICAL + EPSS > 30%, no patch available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Immediate

Exploitation· derived

Active

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

Very High

Priority Score

170

Low Medium High Critical

KEV: 0

EPSS: +86

CVSS: +49

PoC: +20

Weaponized: +15

Threat intel: 0

Gov advisory: 0

Attack Technique

Privilege Escalation HIGH

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.