# CVE-2026-16954: AI Engine < 3.6.4 - Editor+ Sensitive Information Disclosure of API Key and Bearer Tokens

> Editors can read stored API keys and tokens in cleartext due to missing redaction in admin scripts, exposing sensitive third-party credentials.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-9wjr-j39x-f62m

## What is CVE-2026-16954?

CVE-2026-16954 is a medium-severity vulnerability in Unknown AI Engine, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-16954?


## How do I fix CVE-2026-16954?

No fix has been published for CVE-2026-16954 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16954 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16954 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16954 and fix it if it is affected.

What it is: CVE-2026-16954 is a medium-severity vulnerability in Unknown AI Engine, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16954 exists.

Affected product: Unknown AI Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16954/ (Markdown: https://insights.sbomify.com/CVE-2026-16954/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16954
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16954
- OSV: https://osv.dev/vulnerability/CVE-2026-16954

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16954/
Summaries are generated and may contain mistakes; the official description above is the record.