CVE-2025-40894
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stored HTML injection vulnerability exists in the Alerted Nodes Dashboard where authenticated privileged users can inject arbitrary HTML into node labels. When those nodes trigger alerts and are displayed in the dashboard, the malicious HTML renders in victims' browsers, enabling phishing and open redirect attacks. Full XSS and direct information disclosure are blocked by existing input validation and CSP.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 25.6.0< 25.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionDetermine if you are running Nozominetworks CMC or Guardian, then check the installed version against the affected range (less than 25.6.0). Consult your product's about or version information page.Affected if The product is CMC or Guardian and the version is below 25.6.0
-
Confirm Alerted Nodes Dashboard is accessibleLocate the Alerted Nodes Dashboard feature in your deployment and verify it is enabled and accessible to users. This is the component where the injection renders.Affected if The Alerted Nodes Dashboard feature is enabled and users can view triggered alerts with node labels
-
Identify privileged user accessDetermine if any authenticated users in your system have privileged access permissions, as the vulnerability requires a privileged user to inject the HTML into node labels.Affected if Privileged user accounts exist that can modify node label fields
-
Inspect node label configuration storageExamine the database or configuration store where node labels are saved. Look for any node label entries that may contain raw HTML tags (such as <a>, <img>, <iframe>, <form>) that have not been escaped or stripped.Affected if Node labels in storage contain unescaped HTML markup that would render as raw HTML when displayed in the dashboard
Your environment is affected if you are running CMC or Guardian version below 25.6.0, the Alerted Nodes Dashboard is active, privileged users can modify node labels, and any node labels contain raw HTML that will render in the dashboard view.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped25.6.0
Implement strict input validation and output encoding on node label fields to strip or escape HTML tags before storage and rendering.
Cmc and Guardian version 25.6.0 or later
- 1. Identify all deployments running Cmc or Guardian versions prior to 25.6.0
- 2. Schedule a maintenance window for the upgrade process
- 3. Back up current configuration and data according to standard backup procedures
- 4. Upgrade Cmc to version 25.6.0 or later
- 5. Upgrade Guardian to version 25.6.0 or later
- 6. Verify the upgrade was successful by checking the software version
- 7. Test the Alerted Nodes Dashboard functionality to confirm the vulnerability is remediated
- 8. Confirm that HTML injection is no longer possible in node label input fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data