# CVE-2026-6404: Anomify AI <= 0.3.6 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'anomify_api_key' Parameter

> Authenticated administrators can inject arbitrary scripts via the API key parameter, leading to stored XSS execution on the settings page.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-58gg-mqhx-3cgq

## What is CVE-2026-6404?

CVE-2026-6404 is a medium-severity cross-site scripting vulnerability in simonholliday Anomify AI – Anomaly Detection and Alerting, published on 20 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Anomify AI – Anomaly Detection and Alerting plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'anomify_api_key' parameter in versions up to and including 0.3.6. This is due to insufficient input sanitization and missing output escaping: the plugin applies sanitize_text_field() to the Metric Data Key input before saving it via update_option(), but sanitize_text_field() strips HTML tags without encoding double-quote characters, and the value is then echoed directly into an HTML attribute context (value="...") without esc_attr(). This makes it possible for authenticated attackers with administrator-level access to inject arbitrary web scripts that execute whenever a user visits the plugin's settings page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-6404 being exploited?

There is no known exploitation of CVE-2026-6404 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6404 is a medium-severity cross-site scripting vulnerability in simonholliday Anomify AI – Anomaly Detection and Alerting, published on 20 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6404 in the wild and no public exploit code.

Affected product: simonholliday Anomify AI – Anomaly Detection and Alerting. 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-6404/ (Markdown: https://insights.sbomify.com/CVE-2026-6404/index.md)
```

## Sources

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

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