CVE-2026-75798

AI Engine – The Chatbot, AI Framework & MCP for WordPress 3.4.0 - 3.7.1 - Missing Authorization to Unauthenticated Arbitrary AI Query Execution

2026-08-28 00:00
Abdullah Kareem

Strategic Overview

Status
Patched in 3.7.2
Affected Plugin
AI Engine – The Chatbot, AI Framework & MCP for WordPress
Affected Version
3.4.0 – 3.7.1
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-75798
View all AI Engine – The Chatbot, AI Framework & MCP for WordPress vulnerabilities

At a glance

CVE-2026-75798 is a medium-severity Missing Authorization vulnerability in the AI Engine WordPress plugin, affecting versions 3.4.0 – 3.7.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.2; sites on affected versions should update now. Disclosed August 2026, reported by Abdullah Kareem.

Vulnerability Overview

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions 3.4.0 to 3.7.1. This makes it possible for unauthenticated attackers to execute arbitrary AI queries.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in AI Engine 3.4.0 – 3.7.1 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For AI Engine the fix is 3.7.2: builds 3.4.0 – 3.7.1 are affected, anything from 3.7.2 onward is not.

Remediation

Update to version 3.7.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: AI Engine 3.7.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-75798https://www.wordfence.com/threat-intel/vulnerabilities/id/ef4dad25-f1e1-401c-91c3-525c045bddf6https://nvd.nist.gov/vuln/detail/CVE-2026-75798

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C