CVE-2025-11749: 
WordPress vulnerability analysis and mitigation

Overview

The AI Engine WordPress plugin contains a critical Sensitive Information Exposure vulnerability (CVE-2025-11749) affecting all versions up to and including 3.1.3. The vulnerability was discovered in November 2025 and impacts over 100,000 WordPress installations. The plugin, which integrates large language models like ChatGPT and Claude into WordPress, exposes sensitive authentication tokens through its Model Context Protocol (MCP) feature via the /mcp/v1/ REST API endpoint (SecurityOnline Info, Wordfence Blog).

Technical details

The vulnerability stems from improper implementation of REST API routes in the Meow_MWAI_Labs_MCP class, where the 'No-Auth URL' endpoints are registered publicly without proper restrictions. Specifically, the endpoints lack the 'show_in_index => false' parameter, resulting in the exposure of bearer tokens within the REST API index. The vulnerability has received a CVSS score of 9.8 (Critical), indicating its severe nature (SecurityOnline Info).

Impact

When exploited, this vulnerability allows unauthenticated attackers to extract bearer tokens and gain full access to the MCP, enabling them to execute various commands including 'wp_update_user'. This can lead to privilege escalation to administrator status, potentially resulting in complete site takeover, backdoor installation, SEO spam injection, or malicious redirects (SecurityOnline Info).

Exploitability

The vulnerability is actively being exploited in the wild, with Wordfence reporting six exploitation attempts within 24 hours of public disclosure. Exploitation is only possible when the 'No-Auth URL' feature is enabled, though administrators may have unknowingly activated this during configuration testing or API integration (SecurityOnline Info).

Mitigation and workarounds

A patch has been released in version 3.1.4 of the AI Engine plugin. Site administrators are strongly advised to update to this version immediately. For those unable to update immediately, ensuring the 'No-Auth URL' feature is disabled serves as a temporary mitigation measure (SecurityOnline Info).

Community reactions

The vulnerability was discovered and reported by security researcher Emiliano Versini through the Wordfence Bug Bounty Program, earning a bounty of $2,145. The discovery was made just one day after the vulnerable code was introduced (SecurityOnline Info).

Additional resources


Source: This report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-19907CRITICAL9.8
  • shipo
NoYesNov 14, 2026
CVE-2026-18053HIGH8.8
  • memberdash
NoYesNov 14, 2026
CVE-2026-116753HIGH7.2
  • cf7-multi-step
NoYesNov 14, 2026
CVE-2026-110531MEDIUM6.4
  • fv-player
NoYesNov 14, 2026
CVE-2026-127115MEDIUM5.4
  • buddyforms
NoYesNov 14, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management