CVE-2026-15988 Overview
CVE-2026-15988 is a Cross-Site Request Forgery (CSRF) vulnerability [CWE-352] affecting the AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin. All versions up to and including 3.6.5 are vulnerable due to missing or incorrect nonce validation on the reauth_for_authorize function. Unauthenticated attackers can create new administrator accounts by tricking a site administrator into clicking a malicious link. The bypass leverages WordPress's ?_method=POST method-override support to convert a top-navigation GET request into an authenticated POST to the REST users endpoint, requiring no existing account on the attacker's side.
Critical Impact
Successful exploitation grants attackers full administrator access to the WordPress site, enabling site takeover, malicious plugin installation, and persistent backdoor placement.
Affected Products
- AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin, versions up to and including 3.6.5
- Fixed in AI Engine version 3.6.6
- WordPress installations exposing the plugin's OAuth reauthorization flow
Discovery Timeline
- 2026-08-01 - CVE-2026-15988 published to NVD
- 2026-08-03 - Last updated in NVD database
Technical Details for CVE-2026-15988
Vulnerability Analysis
The vulnerability resides in the reauth_for_authorize function within labs/mcp-oauth.php of the AI Engine plugin. The function processes authorization requests without validating a WordPress nonce token, breaking the standard CSRF defense mechanism. An attacker can craft a malicious page or link that, when visited by an authenticated administrator, silently issues a state-changing request to the plugin's OAuth endpoint.
The attack chains together CSRF with WordPress's built-in HTTP method-override behavior. By appending ?_method=POST to a GET request, an attacker converts a top-level navigation event into an authenticated POST against the REST users endpoint. This effectively bypasses the requirement for the attacker to hold any valid session on the target site.
Root Cause
The root cause is missing or incorrect nonce validation in the reauth_for_authorize handler. WordPress plugins are expected to validate a nonce token on any state-changing request to prove the request originated from a legitimate user interaction on the site. The AI Engine plugin's OAuth reauthorization flow omits this check, allowing forged cross-origin requests to reach privileged code paths.
Attack Vector
Exploitation requires user interaction from a logged-in administrator. The attacker hosts a page containing a link or auto-submitting element pointing to the vulnerable endpoint with ?_method=POST and parameters that create a new administrator account with attacker-controlled credentials. When the administrator clicks the link, the browser sends existing authentication cookies, and the plugin processes the request as legitimate. The vulnerability exposes confidentiality, integrity, and availability of the site since the resulting account has full administrative privileges.
No verified public exploit code is available. See the Wordfence Vulnerability Report and the WordPress AI Engine Code Reference for technical detail on the affected function.
Detection Methods for CVE-2026-15988
Indicators of Compromise
- Newly created WordPress administrator accounts with unfamiliar usernames or email addresses
- HTTP requests to the WordPress REST users endpoint containing the _method=POST query parameter
- Referer headers pointing to external, untrusted domains on requests targeting mcp-oauth.php or the AI Engine plugin routes
- Unexpected entries in the WordPress wp_users and wp_usermeta tables added shortly after an administrator followed an external link
Detection Strategies
- Alert on any WordPress REST API user-creation request that arrives with an HTTP method-override parameter such as ?_method=POST
- Monitor plugin file activity for changes to labs/mcp-oauth.php and audit calls to the reauth_for_authorize function
- Correlate administrator browser activity with subsequent role assignments to identify request-forgery patterns
Monitoring Recommendations
- Ingest WordPress access logs and PHP error logs into a centralized analytics platform to enable historical query of REST endpoint activity
- Track creation of accounts with the administrator role and generate alerts on any occurrence outside approved provisioning workflows
- Monitor outbound web traffic from administrator workstations for known malicious CSRF landing pages
How to Mitigate CVE-2026-15988
Immediate Actions Required
- Update the AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin to version 3.6.6 or later on all WordPress sites
- Audit the WordPress user list for unexpected administrator accounts and remove any that cannot be attributed to a legitimate operator
- Rotate credentials and session tokens for all administrator accounts on affected sites
Patch Information
The vendor released a fix in AI Engine 3.6.6. The corrective changes are documented in the WordPress AI Engine Change Log and the OAuth handler changeset. Applying the patch restores nonce validation on the reauth_for_authorize function and closes the method-override bypass path.
Workarounds
- Disable or deactivate the AI Engine plugin until the site can be updated to version 3.6.6
- Restrict access to the WordPress admin interface using IP allow-lists or a web application firewall rule that blocks requests containing _method=POST
- Require administrators to use separate browser profiles or sessions when performing WordPress administration to reduce CSRF exposure
# Example WAF rule to block method-override requests to the REST users endpoint
# ModSecurity syntax
SecRule REQUEST_URI "@rx /wp-json/wp/v2/users" \
"chain,deny,status:403,id:1015988,msg:'Block WP method-override to users endpoint (CVE-2026-15988)'"
SecRule ARGS:_method "@streq POST"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
