CVE-2025-40904
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 HTML Injection vulnerability was discovered in the Smart Polling functionality due to improper validation of an input parameter. An authenticated user with limited privileges can push malicious remote strategies containing HTML tags through the sync. When a victim views the affected remote strategy in the Smart Polling functionality, the injected HTML renders in their browser, 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.
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 HTML injection vulnerability exists in the Smart Polling functionality where the sync feature accepts remote strategies without proper validation of an input parameter. An authenticated low-privilege user can inject malicious HTML tags into a remote strategy, which persists and renders when other users view that strategy in the Smart Polling interface. While full XSS and information disclosure are blocked by existing input validation and CSP, the injected HTML enables phishing and potential open redirect attacks.
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< 26.1.0< 26.1.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 the installed version of Nozomi Networks CMC or GuardianAccess the product console or use the command line interface to retrieve the version number. Typically found in About section or via CLI command like 'system status' or 'version display'.Affected if The version is lower than 26.1.0, meaning the product is vulnerable to the HTML injection flaw.
-
Verify if Smart Polling feature is enabledNavigate to the product settings or configuration panel and locate the Smart Polling module status. Check the management interface under Polling or Monitoring settings.Affected if Smart Polling is enabled and the product version is below 26.1.0, the vulnerability can be exploited.
-
Check for existing remote strategies in Smart PollingAccess the Smart Polling configuration screen and review any configured remote strategies. Look for entries under the sync or remote strategy sections.Affected if Remote strategies exist and the version is vulnerable, injected HTML could persist and render for other users viewing those strategies.
-
Identify if low-privilege users have access to the sync featureReview user role permissions in the access control or user management section. Determine if standard or low-privilege users can access the strategy sync functionality.Affected if Low-privilege authenticated users can access the sync feature on a vulnerable version, they can inject HTML into remote strategies.
A user is affected if they are running CMC or Guardian version below 26.1.0 with Smart Polling enabled and remote strategies accessible to authenticated users.
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 · scoped26.1.0
Implement strict input validation and sanitization on the remote strategy parameter in the sync endpoint, combined with output encoding when rendering strategies in the Smart Polling interface to prevent HTML injection.
Upgrade to Cmc 26.1.0 or later / Guardian 26.1.0 or later
- Identify the current installed version of Cmc or Guardian using the product's version check mechanism
- Backup the current configuration and any custom settings
- Consult the official release notes for version 26.1.0 to review new features, changes, and any known migration requirements
- Upgrade Cmc or Guardian to version 26.1.0 or later following the product's standard upgrade procedure
- After upgrade, verify the Smart Polling functionality works correctly with properly sanitized input
- Confirm the version has been successfully applied by checking the product's about or version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40904 — 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-40904 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