CVE-2026-75796

AI Engine – The Chatbot, AI Framework & MCP for WordPress <= 3.6.0 - Authenticated (Administrator+) Privilege Escalation

2026-08-24 00:00
Charles Vosburgh

Strategic Overview

Status
Patched in 3.6.1
Affected Version
<= 3.6.0
CVSS
4.7Medium
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-75796
View all AI Engine – The Chatbot, AI Framework & MCP for WordPress vulnerabilities

At a glance

CVE-2026-75796 is a medium-severity Improper Privilege Management vulnerability in the AI Engine WordPress plugin, affecting versions <= 3.6.0. It carries a CVSS score of 4.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 3.6.1; sites on affected versions should update now. Disclosed August 2026, reported by Charles Vosburgh.

Vulnerability Overview

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.6.0. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for authenticated attackers, with administrator-level access and above, to elevate their privileges beyond those intended for their role.

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 interaction from a victim user.

CWE-269: Improper Privilege Management

Reaching this weakness in AI Engine <= 3.6.0 takes an account at Administrator level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For AI Engine the fix is 3.6.1: builds <= 3.6.0 are affected, anything from 3.6.1 onward is not.

Remediation

Update to version 3.6.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: AI Engine 3.6.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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