Ai Engine - Security Vulnerability (CVE-2026-110732)

Q: Am I affected by this vulnerability?

You are affected if your site runs Ai Engine. No account is needed to exploit this, so a public site is reachable by anyone.

Q: How do I fix it?

Update Ai Engine to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

Q: What can an attacker actually do?

This is a Broken Access Control flaw. An attacker who exploits it can reach actions or data that should have been restricted to someone else.

CVE-2026-110732

Vulnerability CVE-2026-110732 PLUGIN ai-engine HIGH

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.

CVE-2026-110732

HIGH CVSS 7.5 Published 2026-10-30 Updated 2026-10-30

AI Risk High (82/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent

Severity Band HIGH

CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected Components 2

Reference Links 8

AI Risk Engine High (82/100)

Exploitability High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-10-30 CVE published and first recorded in the threat feed.
2026-10-30 Record updated with latest vulnerability metadata.
2026-11-07 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 4 days ago

AI enriched 4 days ago (2026-11-07 20:25 UTC)

Technical Summary

Potential Impact

Severity is HIGH (CVSS 7.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 82/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Ai Engine PLUGIN · ai-engine Affected: <= 3.8.6 Fixed version not specified

for WordPress is vulnerable to Missing Authorization in all versions up to PLUGIN · for-wordpress-is-vulnerable-to-missing-authorization-in-all-versions-up-to Affected: <= 3.8.6 Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Ai Engine to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Ai Engine, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?