# CVE-2024-12021: Stored Cross-Site Scripting

> Stored XSS in Coverity admin interfaces allows attackers to compromise local accounts and execute scripts.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-wgw2-48jp-77f3

## What is CVE-2024-12021?

CVE-2024-12021 is a high-severity cross-site scripting vulnerability in Black Duck Coverity, published on 31 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Coverity versions prior to 2024.9.0 are vulnerable to stored cross-site scripting (XSS) in various administrative interfaces. The impact of exploitation may result in the compromise of local accounts managed by the Coverity platform as well as other standard impacts resulting from cross-site scripting.

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

## Which versions are affected by CVE-2024-12021?


## How do I fix CVE-2024-12021?

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

## Is CVE-2024-12021 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12021 and fix it if it is affected.

What it is: CVE-2024-12021 is a high-severity cross-site scripting vulnerability in Black Duck Coverity, published on 31 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12021 in the wild and no public exploit code.

Affected product: Black Duck Coverity. 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-2024-12021/ (Markdown: https://insights.sbomify.com/CVE-2024-12021/index.md)
```

## Sources

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

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