CVE-2025-40892
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 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.
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 · high confidenceA stored XSS vulnerability exists in the Reports functionality where an authenticated user with report privileges can inject malicious JavaScript through a report definition, or a victim can be tricked into importing a malicious report template. When other users view or import these crafted reports, the embedded JavaScript executes in their browser session, enabling session hijacking, data modification, or information disclosure.
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.5.0< 25.5.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:H
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 installed product and versionLocate the Nozomi Networks CMC or Guardian installation and check the software version. This is typically found in the application UI under Help/About, or via the command line interface using 'show version' or similar. Compare the version number against the affected range (anything below 25.5.0).Affected if The installed version of CMC or Guardian is below 25.5.0
-
Verify Reports functionality is accessibleConfirm whether the Reports module or feature is enabled and accessible in your installation. Check user role permissions to determine if the account can access, create, or import reports.Affected if The Reports feature is enabled and accessible to your user account
-
Review existing report definitionsAccess the Reports section of the application and enumerate all saved report definitions. Inspect the report configuration files or templates for any unexpected script tags, JavaScript event handlers, or encoded payloads that may indicate malicious content.Affected if Any report definition contains unsanitized user-supplied content that could execute as JavaScript
-
Check for imported report templatesReview the report import functionality and examine any recently imported report templates or definitions. Look for template files that contain script elements, event attributes, or suspicious data that could be executed when the report is rendered.Affected if There are imported report templates containing potentially malicious scripts
-
Test for XSS execution in browserOpen the Reports view in a web browser and use browser developer tools (F12) to inspect the DOM. Check the Network tab for any unexpected requests and the Console for JavaScript errors or warnings that may indicate XSS payload execution.Affected if JavaScript executes or attempts to execute when viewing or interacting with reports
You are affected if you are running CMC or Guardian version below 25.5.0 and have the Reports functionality enabled with unvalidated report definitions or imported templates present in the system.
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.5.0
Implement proper input validation and output encoding on all report-related parameters, ensuring all user-supplied content is sanitized before storage and properly escaped when rendered. Additionally, implement Content Security Policy headers to mitigate XSS execution.
Cmc 25.5.0 and Guardian 25.5.0
- Identify all deployed instances of Cmc and Guardian in your environment
- Backup all current configurations and data before upgrading
- Upgrade Cmc to version 25.5.0 or later (check security.nozominetworks.com for exact release notes)
- Upgrade Guardian to version 25.5.0 or later (check security.nozominetworks.com for exact release notes)
- After upgrading, verify the version numbers to confirm the update was successful
- Test the Reports functionality to confirm the XSS vulnerability is no longer present
- Verify that all report import and viewing operations properly sanitize input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40892 — 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-40892 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