CVE-2025-3718
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 client-side path traversal vulnerability was discovered in the web management interface front-end due to missing validation of an input parameter. An authenticated user with limited privileges can craft a malicious URL which, if visited by an authenticated victim, leads to a Cross-Site Scripting (XSS) attack.
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 client-side path traversal vulnerability exists in the web management interface front-end where an input parameter is not properly validated. An authenticated attacker with limited privileges can craft a malicious URL containing path traversal sequences that, when visited by another authenticated victim, executes arbitrary JavaScript code in the victim's browser (reflected XSS).
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.2.0< 25.2.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 installed Nozominetworks productCheck system for installed Nozominetworks CMC or Guardian. Look for installation directories, running services, or check product documentation for installed software locations.Affected if Nozominetworks CMC or Guardian is present on the system
-
Check product version numberLocate and read the version file or use the product's CLI command to retrieve the installed version (such as 'show version' or checking version files in installation directories). Compare against 25.2.0.Affected if Installed version is below 25.2.0
-
Verify web management interface is enabledConfirm the web management interface service is running and accessible. Check if port 443 or the web interface URL responds.Affected if Web management interface is accessible and exposed
-
Inspect URL parameters for path traversalReview web application traffic or proxy logs for requests containing '../' sequences in URL parameters. Manually test suspicious endpoints by adding path traversal sequences to parameters.Affected if URL parameters accept and reflect path traversal sequences without sanitization
The environment is affected if Nozominetworks CMC or Guardian is installed with a version below 25.2.0 and the web management interface is enabled, allowing path traversal sequences in URL parameters to reflect as executable JavaScript.
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.2.0
Implement strict input validation on all user-controllable parameters to reject path traversal sequences, and apply contextual output encoding when reflecting user input back to the browser to prevent XSS execution.
CMC and Guardian version 25.2.0 or later
- 1. Identify the current installed versions of CMC (Common Criteria) and Guardian products in your environment
- 2. Download the version 25.2.0 or later release from the official Nozomi Networks support portal
- 3. Review the upgrade documentation and release notes for any pre-upgrade requirements
- 4. Perform the upgrade following the standard upgrade procedure for your deployment (this may include backing up configuration, testing in a staging environment)
- 5. After upgrade, verify the installed version is 25.2.0 or higher
- 6. Confirm the web management interface is functioning correctly and the path traversal vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3718 — 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-3718 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