# CVE-2025-40894: HTML injection in Alerted Nodes Dashboard in Guardian/CMC before 25.6.0

> Authenticated users can inject HTML into node labels, potentially enabling phishing or open redirects in the Alerted Nodes Dashboard.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-p2w9-p68c-qpqg

## What is CVE-2025-40894?

CVE-2025-40894 is a low-severity cross-site scripting vulnerability in Nozomi Networks CMC, published on 4 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Stored HTML Injection vulnerability was discovered in the Alerted Nodes Dashboard functionality due to improper validation on an input parameter.

A malicious authenticated user with the required privileges could edit a node label to inject HTML tags. If the system is configured to use the Alerted Nodes Dashboard, and alerts are reported for the affected node, then the injected HTML may render in the browser of a victim user interacting with it, 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-40894?

It affects 2 products.


Products: Nozominetworks Cmc, Nozominetworks Guardian.

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

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

## Is CVE-2025-40894 being exploited?

There is no known exploitation of CVE-2025-40894 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-40894 and fix it if it is affected.

What it is: CVE-2025-40894 is a low-severity cross-site scripting vulnerability in Nozomi Networks CMC, published on 4 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-40894 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-40894/ (Markdown: https://insights.sbomify.com/CVE-2025-40894/index.md)
```

## Sources

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

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