# CVE-2025-40893: HTML injection in Asset List in Guardian/CMC before 25.5.0

> Unauthenticated attackers can inject HTML into asset lists via network packets, enabling phishing or open redirects when victims view the assets.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-wg8q-pmvg-p6gw

## What is CVE-2025-40893?

CVE-2025-40893 is a medium-severity cross-site scripting vulnerability in Nozomi Networks CMC, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Stored HTML Injection vulnerability was discovered in the Asset List functionality due to improper validation of network traffic data. An unauthenticated attacker can send specially crafted network packets to inject HTML tags into asset attributes. When a victim views the affected assets in the Asset List (and similar functions), the injected HTML renders in their browser, enabling phishing and possibly open redirect attacks. Full XSS exploitation and direct information disclosure are prevented by the existing input validation and Content Security Policy configuration.

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

## Which versions are affected by CVE-2025-40893?

It affects 2 products.


Products: Nozominetworks Cmc, Nozominetworks Guardian.

## How do I fix CVE-2025-40893?

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

## Is CVE-2025-40893 being exploited?

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

## Other vulnerabilities in Nozomi Networks CMC

- [CVE-2023-29245](https://insights.sbomify.com/CVE-2023-29245/): SQL Injection on IDS parsing of malformed asset fields in Guardian/CMC >= 22.6.0 before 22.6.3 and 23.1.0 (critical 9.2)
- [CVE-2026-31984](https://insights.sbomify.com/CVE-2026-31984/): DoS through oversized audit log entries in Guardian/CMC before 26.2.0 (high 8.7)
- [CVE-2023-2567](https://insights.sbomify.com/CVE-2023-2567/): Authenticated SQL Injection on Query functionality in Guardian/CMC before 22.6.3 and 23.1.0 (high 8.7)
- [CVE-2023-22378](https://insights.sbomify.com/CVE-2023-22378/): Authenticated Blind SQL Injection on sorting in Guardian/CMC before 22.6.2 (high 8.7)
- [CVE-2023-23574](https://insights.sbomify.com/CVE-2023-23574/): Authenticated Blind SQL Injection on alerts count in Guardian/CMC before 22.6.2 (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40893 and fix it if it is affected.

What it is: CVE-2025-40893 is a medium-severity cross-site scripting vulnerability in Nozomi Networks CMC, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-40893 in the wild and no public exploit code.

Affected product: Nozomi Networks CMC. 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-2025-40893/ (Markdown: https://insights.sbomify.com/CVE-2025-40893/index.md)
```

## Sources

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

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