The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Missing
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 30 Oct 2026, 10:31 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| tigroumeowAI Engine – MCP Server & AI Chatbot for WordPress, with Claude, ChatGPT & Gemini | Affected
| Fixed in– |
AI-suggested
Until a fix is available, administrators should be cautious when approving OAuth clients on the consent screen and consider implementing manual controls or monitoring for suspicious OAuth client registrations. Additionally, applying web server or security plugin rules to add X-Frame-Options and Content-Security-Policy frame-ancestors headers to the consent page can help mitigate clickjacking risks.
Description
The AI Engine WordPress plugin up to version 3.8.6 has a Missing Authorization vulnerability in its MCP module's OAuth 2.1 Dynamic Client Registration endpoint. This flaw allows unauthenticated users to register OAuth clients with attacker-controlled redirect URIs. If an administrator approves the malicious client on the OAuth consent screen, attackers can gain administrator-level control, including user creation and option updates. The consent page lacks protections against clickjacking, increasing the risk of unauthorized approval.
References
- nvd.nist.gov/vuln/detail/CVE-2026-110732 (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.8.3/labs/mcp-oauth.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.8.3/labs/mcp-oauth.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.8.3/labs/mcp-oauth.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.8.3/labs/mcp-oauth.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ai-engine/tags/3.8.3/labs/mcp.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3760851/ai-engine/trunk/labs/mcp-oauth.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&new=3760852%40ai-engine%2Ftags%2F3.8.7&old=3757660%40ai-engine%2Ftags%2F3.8.6 (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/eb115a8a-35f8-426f-bb67-4a523f67cb34?source=cve (opens in a new tab)