CVE-2026-16954

AI Engine <= 3.6.3 - Authenticated (Editor+) Information Exposure

Strategic Overview

Status
Patched in 3.6.4
Affected Version
<= 3.6.3
CVSS
2.7Low
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-16954
View all AI Engine – The Chatbot, AI Framework & MCP for WordPress vulnerabilities

At a glance

CVE-2026-16954 is a low-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the AI Engine WordPress plugin, affecting versions <= 3.6.3. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 3.6.4; sites on affected versions should update now. Disclosed July 2026, reported by Revanth Hari Narayana Matte.

Vulnerability Overview

The AI Engine plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.6.3. This makes it possible for authenticated attackers, with editor-level access and above, to extract sensitive user or configuration data.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in AI Engine <= 3.6.3 takes an account at Editor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For AI Engine the fix is 3.6.4: builds <= 3.6.3 are affected, anything from 3.6.4 onward is not.

Remediation

Update to version 3.6.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: AI Engine 3.6.4 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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