dbcve.org
CmcApplication · Nozominetworks

CVE-2025-40893

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 25.5.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A Stored HTML Injection vulnerability was discovered in the Asset List functionality due to improper validation of network traffic data. An unauthenticated attacker can send specially crafted network packets to inject HTML tags into asset attributes. When a victim views the affected assets in the Asset List (and similar functions), 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 · moderate confidence

A stored HTML injection vulnerability exists in the Asset List functionality where improper validation of network traffic data allows unauthenticated attackers to inject HTML tags into asset attributes. When users view these affected assets, the HTML renders in their browser, enabling phishing and potential open redirect attacks.

MitigationImplement strict input validation and sanitization for network traffic data before storing in asset attributes, ensuring all HTML/script tags are stripped or properly encoded at the point of ingestion.

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
CmcApplication
Affected:< 25.5.0
GuardianApplication
Affected:< 25.5.0

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed version of Nozominetworks CMC
    Access the CMC administrative interface and navigate to System > About or use the CLI command 'cmc --version' to retrieve the exact version number
    Affected if The version is less than 25.5.0
  2. Check installed version of Nozominetworks Guardian
    Access the Guardian administrative interface and navigate to System > About or use the CLI command 'guardian --version' to retrieve the exact version number
    Affected if The version is less than 25.5.0
  3. Verify Asset List functionality accessibility
    Navigate to the Asset List feature in the web interface under Assets > Asset List to confirm the feature is accessible and in use
    Affected if The Asset List feature is accessible and contains any assets
  4. Inspect asset attributes for suspicious HTML content
    Review each asset entry in the Asset List, specifically examining network traffic-related fields such as hostname, IP address, device name, or custom attributes for injected HTML tags like <script>, <iframe>, <a href>, or other HTML markup
    Affected if Any asset attribute contains unescaped HTML tags or script elements that render when viewed
  5. Review asset creation logs for unauthorized entries
    Examine audit logs or asset creation logs for entries showing asset creation from unauthenticated or unexpected sources, particularly entries with HTML or JavaScript content in data fields
    Affected if Logs show asset creation attempts containing HTML/script tags or entries created by unauthenticated sources

A user is affected if either CMC or Guardian is installed at a version below 25.5.0 AND the Asset List feature is accessible with assets containing unescaped HTML content in their attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 25.5.0 or later
Fixed in 25.5.0
Interim mitigation

Implement strict input validation and sanitization for network traffic data before storing in asset attributes, ensuring all HTML/script tags are stripped or properly encoded at the point of ingestion.

Recommended fix High confidence

25.5.0

  1. 1. Identify whether the Cmc or Guardian product is deployed in your environment
  2. 2. Check the current version of the installed product (Cmc or Guardian)
  3. 3. Create a backup of the current configuration according to standard backup procedures
  4. 4. Upgrade Cmc to version 25.5.0 or later
  5. 5. Upgrade Guardian to version 25.5.0 or later
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Confirm the Asset List functionality works correctly and that injected HTML tags are no longer rendered

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-40893 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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