CVE-2026-110732

HighCVSS 7.5

Published: 30/10/2026(UTC)Updated: 30/10/2026(UTC)Translated: 30/10/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.27%

20th percentile - higher than 20% of all known CVEs

Summary

The AI Engine – The Chatbot, AI Framework & MCP plugin for WordPress in versions up to and including 3.8.6 is vulnerable to Missing Authorization. The MCP module's OAuth 2.1 Dynamic Client Registration endpoint (/wp-json/mcp/v1/oauth/register) is registered with a permission_callback of __return_true, allowing an unauthenticated user to register an active OAuth client with an attacker-controlled redirect URI. Once an administrator approves the attacker's client on the OAuth consent screen, the attacker can obtain an administrator-bound MCP access token and gain full administrator-level control; the consent page lacks X-Frame-Options or CSP frame-ancestors, enabling clickjacking.

Risk Assessment

An attacker can gain full administrator privileges through MCP tools, including user creation and option updates, leading to complete site takeover.

Recommendation

Update the AI Engine plugin to a version later than 3.8.6 and consider disabling the MCP module until the fix is applied.

Other vulnerabilities in AI Engine – The Chatbot, AI Framework & MCP

CVE-2026-15988High
The AI Engine – The Chatbot, AI Framework & MCP plugin for WordPress is vulnerable to Cross-Site Request Forgery due to missing nonce validation on the `reauth_for_authorize` function. Unauthenticated attackers can trick an administrator into clicking a link, allowing creation of a new administrator account with attacker-supplied credentials.

Original NVD description (English source)

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.8.6 This is due to the MCP module's OAuth 2.1 Dynamic Client Registration endpoint (/wp-json/mcp/v1/oauth/register) being registered with a permission_callback of __return_true, allowing an unauthenticated user to register an active OAuth client with an attacker-controlled redirect URI. This makes it possible for unauthenticated attackers to obtain an administrator-bound MCP access token, and thereby full administrator-level control through the MCP tools (including user creation and option updates), once an administrator approves the attacker's client on the OAuth consent screen. The consent page is additionally served without X-Frame-Options or Content-Security-Policy frame-ancestors, so that approval can be obtained via clickjacking.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS