CVE-2025-40894: HTML injection in Alerted Nodes Dashboard in Guardian/CMC before 25.6.0
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.
Security readout for executives and security teams
Plain-English summary
An authenticated user with node-label editing privileges could store HTML in a node label. In specific dashboard conditions, that HTML may display to another user and support phishing or redirection. Sources state existing validation and Content Security Policy limit impact and prevent full XSS and direct information disclosure.
Executive priority
Treat as a moderate-priority remediation item. It is not described as actively exploited, but affected OT monitoring environments should patch during the next planned maintenance window and tighten label-editing access.
Technical view
CVE-2025-40894 is stored HTML injection in the Alerted Nodes Dashboard of Nozomi Networks Guardian and CMC before 25.6.0. Exploitation requires authenticated low-privileged access, specific privileges, victim interaction, and dashboard use. CVSS is 4.4 with changed scope, low confidentiality and integrity impact, and no availability impact.
Likely exposure
Exposure appears limited to Nozomi Guardian or CMC deployments before 25.6.0 that use the Alerted Nodes Dashboard and allow users to edit node labels.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Attack practicality is constrained by authentication, required privileges, dashboard configuration, alerts for the affected node, and user interaction.
Researcher notes
Key constraints are important: this is stored HTML injection, not confirmed full XSS. Existing validation and CSP reportedly prevent full XSS exploitation and direct information disclosure. Validate exposure through version, dashboard configuration, alert generation, and RBAC review.
Mitigation direction
Upgrade Guardian and CMC to 25.6.0 or later per vendor guidance.
Restrict node-label editing privileges to trusted administrative roles.
Review whether Alerted Nodes Dashboard use is necessary until patched.
Monitor vendor and Siemens advisories for updated remediation guidance.
Validation and detection
Inventory Guardian and CMC versions and identify systems before 25.6.0.
Confirm whether Alerted Nodes Dashboard is configured and used.
Review accounts with privileges to edit node labels.
Inspect node labels for unexpected HTML-like content.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.