CVE-2025-40895: Nozomi Networks CMC · XSS or 'Cross-site Scripting'
Affects Nozomi Networks CMCSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low : upgrade to 25.6.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 25.6.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Nozomi Networks CMC to 25.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Nozomi NetworksCMC | Affected
| Fixed in
|
AI-suggested
To mitigate this vulnerability, organizations should first ensure strict access control and monitoring of administrator privileges on Guardians connected to the CMC. Limit the number of users with such high-level access and enforce strong authentication mechanisms, including multi-factor authentication. Regularly audit Guardian property changes to detect unauthorized or suspicious modifications. Disable the Sensor Map functionality if it is not essential to reduce the attack surface. Implement additional input validation and sanitization on the server side for all properties that can be edited by administrators to prevent injection of HTML or script content. Review and strengthen Content Security Policy configurations to further restrict the execution of injected content. Stay informed about vendor patches or updates addressing this vulnerability and apply them promptly once available. Conduct user awareness training to recognize phishing attempts that might arise from this vulnerability. Finally, consider network segmentation to isolate CMC components and reduce the impact of compromised credentials.
Description
A Stored HTML Injection vulnerability was discovered in the CMC's Sensor Map functionality due to improper validation on connected Guardians' properties. A malicious authenticated user with administrator privileges on a Guardian connected to a CMC can edit the Guardian's properties to inject HTML tags. If the Sensor Map functionality is enabled in the CMC, when a victim CMC user interacts with it, then the injected HTML may render 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.