Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability presents HIGH real-world risk across multiple dimensions: (1) CVSS 8.8 indicates high severity with network-based attack vector (AV:N), low complexity (AC:L), and low privilege requirements (PR:L), enabling widespread exploitation; (2) The PR:L rating is critical—it requires only subscriber-level access, the lowest user tier in WordPress, making exploitation trivial on sites with user registration enabled; (3) The impact is comprehensive (C:H/I:H/A:H), affecting confidentiality, integrity, and availability through user escalation, data modification, and deletion; (4) Automatable exploitation is high—no user interaction required (UI:N) and no special network conditions (S:U); (5) Organizations with public registration or community sites face immediate risk; (6) The vulnerability enables cascading attacks: privilege escalation to admin, followed by plugin installation, backdoor deployment, or site defacement. While no active KEV/CISA listing or public POC is noted in the provided data, the straightforward nature of the flaw (missing authorization check) makes exploitation trivial once discovered, suggesting high EPSS probability. Priority: CRITICAL for sites with user registration; HIGH for private/restricted-access sites. |
| Exploit ScenarioDerived | An attacker with a free account on a WordPress site using AI Engine 2.8.0–2.8.3 (subscriber-level access, the default for self-registered users) navigates to or discovers the MCP endpoint. Without authentication barriers, the attacker invokes the 'wp_create_user' command via the MCP interface to create a new administrator account with full site privileges. The missing capability check in 'can_access_mcp' allows this subscriber-level request to execute. Once elevated to admin, the attacker installs a malicious plugin, modifies site content via 'wp_update_post', or deploys a backdoor. Alternatively, the attacker uses 'wp_delete_post' to remove critical business pages, 'wp_update_option' to disable security plugins, or 'wp_delete_comment' to cover tracks. No user interaction is required, and the attack is fully automated. On a site with public registration, exploitation is possible within minutes of account creation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 15, 2026
The AI Engine WordPress plugin (versions 2.8.0-2.8.3) contains a missing capability check in the 'Meow_MWAI_Labs_MCP::can_access_mcp' function, allowing authenticated subscribers and above to access the Model Context Protocol (MCP) interface and execute arbitrary WordPress administrative commands. This enables privilege escalation, unauthorized user creation/modification, and data destruction through post and comment manipulation. The vulnerability has a CVSS score of 8.8 (High) and poses immediate risk to any WordPress installation running affected versions with user registration enabled.
Earlier versions of this analysis (1)
The AI Engine WordPress plugin (versions 2.8.0–2.8.3) contains a missing capability check in the 'Meow_MWAI_Labs_MCP::can_access_mcp' function, allowing authenticated subscribers and above to access the Model Context Protocol (MCP) interface and execute arbitrary WordPress administrative commands. This enables privilege escalation, unauthorized user creation/modification, and data destruction through post and comment manipulation. The vulnerability has a CVSS score of 8.8 (High) and poses immediate risk to any WordPress installation running affected versions with user registration enabled.
RemediationAI
Immediate actions: (1) Update AI Engine plugin to version 2.8.4 or later immediately—this patch version includes the missing capability check in 'Meow_MWAI_Labs_MCP::can_access_mcp'. (2) If immediate patching is not possible, disable the AI Engine plugin entirely until a patch is applied. (3) For sites that cannot update quickly, restrict user registration to trusted accounts only and audit user roles to remove unnecessary subscriber-level accounts. (4) Monitor WordPress audit logs and MCP function execution logs for suspicious 'wp_create_user', 'wp_update_user', 'wp_update_option', 'wp_delete_post', and 'wp_delete_comment' calls from low-privilege users. (5) Implement Web Application Firewall (WAF) rules to block MCP requests from non-administrator sources. (6) Review and revoke any suspicious administrator accounts created after plugin installation. Vendor patch location: Consult the official Meow Apps plugin repository on WordPress.org; patch released in version 2.8.4.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the AI Engine plugin's MCP (Model Context Protocol) implementation, specifically in the capability verification layer. The 'can_access_mcp' function fails to enforce WordPress capability checks before allowing access to sensitive MCP commands. CWE-863 (Incorrect Authorization) indicates the root cause is improper validation of user permissions against the WordPress role-based access control (RBAC) system. The affected plugin integrates AI capabilities via MCP, which provides a command execution interface. Authenticated users at subscriber level and above can bypass authorization controls and invoke functions like 'wp_create_user', 'wp_update_user', 'wp_update_option', 'wp_update_post', 'wp_delete_post', 'wp_update_comment', and 'wp_delete_comment'—all of which normally require administrator privileges. The missing check violates the principle of least privilege and breaks WordPress's capability delegation model.
Know when Ai Engine 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
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
The AI Engine plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the 'Meow_MWAI_Labs_MCP::can_access_mcp' function in versions 2.8.0 to 2.8.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to have full access to the MCP and run various commands like 'wp_create_user', 'wp_update_user' and 'wp_update_option', which can be used for privilege escalation, and 'wp_update_post', 'wp_delete_post', 'wp_update_comment' and 'wp_delete_comment', which can be used to edit and delete posts and comments.
Executive ViewAI
WordPress sites using the AI Engine plugin (versions 2.8.0-2.8.3) face significant risk of unauthorized account creation, privilege escalation, and content destruction by low-level users. Any organization running this plugin requires immediate patching to prevent attackers from gaining administrative control and manipulating or deleting critical business content.
Apply vendor patch. If immediate patching is not possible: disable AI Engine plugin entirely; restrict subscriber-level user creation; implement WAF rules blocking requests to wp-admin/admin-ajax.php containing 'mcp' or 'can_access_mcp' parameters; segment WordPress environments from production systems; monitor for suspicious user creation, option updates, and post/comment deletions by low-privileged accounts.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Unrestricted file upload in Jordy Meow's AI Engine: ChatGPT Chatbot plugin for WordPress (versions up to and including 1
Arbitrary file write in the AI Engine WordPress plugin before 3.5.5 lets authenticated editor-level users abuse an unsan
Path traversal in the AI Engine WordPress plugin (versions 3.3.3 through 3.7.1) allows arbitrary server file reads with
Privilege escalation in the AI Engine WordPress plugin (versions 2.8.0 through 3.6.0) enables any sub-site Administrator
The AI Engine WordPress plugin before 2.6.5 does not sanitize and escape a parameter from one of its RESP API endpoint b
AI Engine < 2.4.3 is susceptible to remote-code-execution (RCE) via Log Poisoning. Rated high severity (CVSS 7.2), this
Server-Side Request Forgery (SSRF) vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.1.4. Rated medium severity (CV
Cleartext exposure of third-party API keys and authentication tokens in AI Engine WordPress plugin (before 3.6.4) allows
Unauthorized access to private chatbot conversations in the AI Engine WordPress plugin before 3.5.5 allows any authentic
Unauthenticated remote attackers can invoke AI queries against a site owner's configured provider account through the AI
Unrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.2.63. Rated criti
Unrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.1.4. Rated critic
EUVD-2025-28374
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB