CVE-2025-40892: Stored Cross-Site Scripting (XSS) in Reports in Guardian/CMC before 25.5.0
A Stored Cross-Site Scripting vulnerability was discovered in the Reports functionality due to improper validation of an input parameter. An authenticated user with report privileges can define a malicious report containing a JavaScript payload, or a victim can be socially engineered to import a malicious report template. When the victim views or imports the report, 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
A logged-in attacker with report privileges, or someone who tricks a user into importing a malicious report, can make JavaScript run in the victim’s browser. This could let the attacker alter application data, disrupt availability, or access limited sensitive information using the victim’s permissions.
Executive priority
Prioritize remediation promptly because successful exploitation could modify operational data or disrupt application availability through a victim’s session. Focus first on pre-25.5.0 deployments with broadly assigned report privileges or frequent template imports. Validate exact applicability with Nozomi because the supplied version metadata is internally inconsistent.
Technical view
CVE-2025-40892 is stored cross-site scripting in Guardian and CMC report handling caused by insufficient input validation. A crafted report or imported template executes when viewed or imported. CVSS 3.1 rates it 8.9: network-accessible, low complexity, low privileges, user interaction required, with changed scope and potentially high integrity and availability impact.
Likely exposure
Potential exposure includes Guardian or CMC releases before 25.5.0 where users can create, import, or view reports. Authentication and report privileges constrain direct creation, but social engineering can target users who import templates. The bundle’s structured affected-version data is inconsistent with its title, so confirm exact releases against Nozomi’s advisory.
Exploitation context
The supplied evidence describes plausible authenticated and social-engineering attack paths but provides no evidence of active exploitation. This CVE is not listed as KEV in the bundle. Absence from KEV does not establish that exploitation has never occurred.
Researcher notes
The weakness is CWE-79 stored XSS with required victim interaction and browser-context execution. The stated vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:H. The title identifies versions before 25.5.0, while the structured affected entries contain version “0” and defaultStatus “unaffected”; this discrepancy requires vendor confirmation.
Mitigation direction
Identify Guardian and CMC deployments and record their exact installed versions.
Review Nozomi’s advisory to confirm affected releases and vendor-approved remediation.
Prioritize moving pre-25.5.0 systems to a vendor-supported release identified by Nozomi.
Restrict report creation and import privileges until remediation is confirmed.
Treat externally sourced report templates as untrusted and limit their import.
Validation and detection
Verify each deployment’s product, version, and report functionality exposure.
Confirm remediation status against Nozomi advisory NN-2025:13-01.
Review privileged accounts authorized to create or import reports.
Inspect report and audit records for unexpected templates or unauthorized changes.
Confirm browser-facing report content is safely validated after remediation.
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.