CVE-2026-12510

AI Engine <= 3.5.4 - Authenticated (Subscriber+) Insecure Direct Object Reference to Chatbot Discussion Disclosure

2026-06-25 00:00
Shivamani Vastrala

Strategic Overview

Status
Patched in 3.5.5
Affected Plugin
AI Engine – The Chatbot, AI Framework & MCP for WordPress
Affected Version
<= 3.5.4
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-12510
View all AI Engine – The Chatbot, AI Framework & MCP for WordPress vulnerabilities

At a glance

CVE-2026-12510 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the AI Engine WordPress plugin, affecting versions <= 3.5.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.5.5; sites on affected versions should update now. Disclosed June 2026, reported by Shivamani Vastrala.

Vulnerability Overview

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.5.4 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Custom-level access and above, to read chatbot discussions not belonging to them.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in AI Engine <= 3.5.4 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For AI Engine the fix is 3.5.5: builds <= 3.5.4 are affected, anything from 3.5.5 onward is not.

Remediation

Update to version 3.5.5, 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.5.5 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-12510https://www.wordfence.com/threat-intel/vulnerabilities/id/2bc2c2f8-fb1c-4c37-83d1-d05abd17fbebhttps://nvd.nist.gov/vuln/detail/CVE-2026-12510

Related records

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