Skip to main content
CVE-2026-110732VulnerabilityPublished

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Missing

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-110732· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 10:31 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
tigroumeowAI Engine – MCP Server & AI Chatbot for WordPress, with Claude, ChatGPT & GeminiAffected
  • <=3.8.6
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

Community reviews

Loading reviews…