CVE-2026-16954

AI Engine < 3.6.4 - Editor+ Sensitive Information Disclosure of API Key and Bearer Tokens

Published Aug 6, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
The AI Engine WordPress plugin before 3.6.4 does not redact secret configuration values before exposing them in an admin page's inline script data, allowing users with the Editor role to read the site's stored third-party API key and authentication tokens in cleartext, despite those secrets being restricted to administrators everywhere else.

Analysis

AI-generated

Technical impact

The AI Engine WordPress plugin, before version 3.6.4, fails to redact secret configuration values when rendering them in an admin page’s inline script. This results in a CWE‑200 Information Exposure flaw, allowing users with the Editor role to view the stored third‑party API key and bearer tokens in cleartext, despite those secrets being normally restricted to administrators. An attacker with Editor privileges can thus capture these credentials, using them to compromise external services or gain further access to the site, thereby breaching confidentiality. The likely attack vector is via the web interface when an Editor accesses the admin page.

Affected Systems

Any WordPress site running the AI Engine plugin at a version older than 3.6.4 is affected. The issue arises when the plugin renders configuration data within an admin dashboard page. Editors—or higher roles that can view that page—can read the exposed API keys and bearer tokens. No vendor‑specific product list beyond the generic AI Engine WordPress plugin is provided, and the problem applies to all installations of this plugin before the 3.6.4 release.

Risk and Exploitability

The flaw is exploitable through the web interface and requires a user with Editor privileges, a common role. The CVSS score is 6.5, placing it in the medium severity range, and the EPSS score is <1%, indicating a low probability of exploitation, though it is not listed in the CISA KEV catalog. Because the secrets are presented in plaintext to an elevated‑role user, the security risk remains medium. Exploitation is straightforward: log in as an Editor, open the affected admin page, and copy the inline script containing the credentials; no additional prerequisites are listed.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the AI Engine plugin to version 3.6.4 or later to ensure secret values are properly redacted.
  • Revoke or rotate any exposed API keys and bearer tokens that may have been disclosed before the patch.
  • Restrict Editor role permissions so that they cannot view the admin page where the secrets are rendered, or remove the Editor role from the site until the vulnerability is fixed.

Generated by OpenCVE AI on August 6, 2026 at 17:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions ai Engine
Vendors & Products Wordpress-extensions
Wordpress-extensions ai Engine
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-200
Type Values Removed Values Added
Description The AI Engine WordPress plugin before 3.6.4 does not redact secret configuration values before exposing them in an admin page's inline script data, allowing users with the Editor role to read the site's stored third-party API key and authentication tokens in cleartext, despite those secrets being restricted to administrators everywhere else.
Title AI Engine < 3.6.4 - Editor+ Sensitive Information Disclosure of API Key and Bearer Tokens
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 6, 2026, 2:27 PM
Reserved
Jul 24, 2026, 8:07 AM
Status
Deferred
Published
Aug 6, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM