CVE-2025-40899: Stored Cross-Site Scripting (XSS) in Assets and Nodes in Guardian/CMC before 26.0.0
A Stored Cross-Site Scripting vulnerability was discovered in the Assets and Nodes functionality due to improper validation of an input parameter. An authenticated user with custom fields privileges can define a malicious custom field containing a JavaScript payload. When the victim views the Assets or Nodes pages, the XSS executes in their browser context, allowing the attacker to perform unauthorized actions as the victim, such as modify application data, disrupt application availability, and access limited sensitive information.
Security readout for executives and security teams
Plain-English summary
CVE-2025-40899 is a stored XSS issue in Nozomi Networks Guardian and CMC before 26.0.0. An authenticated user with custom-field privileges can save malicious script content that runs when another user opens Assets or Nodes pages. This could let the attacker act as the victim inside the application.
Executive priority
Treat this as a high-priority remediation for environments using Guardian or CMC, especially in operational technology monitoring contexts. The issue requires authentication, but successful abuse could let a lower-privileged user manipulate the application through a more privileged victim.
Technical view
The issue is CWE-79 improper input validation in Assets and Nodes custom fields. CVSS 3.1 is 8.9, with network access, low attack complexity, low privileges, required user interaction, and changed scope. Impact is described as limited confidentiality loss with high integrity and availability impact.
Likely exposure
Exposure is likely limited to organizations running Nozomi Networks Guardian or CMC before 26.0.0 where authenticated users can define custom fields and other users view Assets or Nodes pages.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. Exploitation requires an authenticated user with custom-field privileges and a victim viewing affected pages. Stored placement raises concern because privileged users may later trigger the script in their browser context.
Researcher notes
Primary signals are the CVE record, CVSS vector, Nozomi advisory, and Siemens advisory. The source bundle identifies Guardian and CMC before 26.0.0, but its affected-version encoding is sparse, so exact version scoping should be validated against vendor guidance.
Mitigation direction
Upgrade Guardian and CMC to 26.0.0 or vendor-advised fixed versions.
Review Nozomi and Siemens advisories for exact affected-version guidance.
Restrict custom-field privileges to trusted administrative users.
Remove or sanitize suspicious custom fields in Assets and Nodes.
Monitor application audit logs for unexpected data changes or availability-impacting actions.
Validation and detection
Inventory deployed Guardian and CMC versions and compare against vendor advisories.
Confirm whether custom-field privileges are assigned to non-administrative users.
Review Assets and Nodes custom fields for embedded script-like content.
Check logs for recent custom-field creation or modification by unusual accounts.
After remediation, verify Assets and Nodes pages render custom fields safely.
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.
2CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.