CVE-2025-40901
Stored HTML Injection in Credentials Manager
Publication date: 2026-05-19
Last updated on: 2026-05-19
Assigner: Nozomi Networks Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nozominetworks | cmc | to 26.1.0 (exc) |
| nozominetworks | guardian | to 26.1.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability involves stored HTML injection that can enable phishing and open redirect attacks, which may increase the risk of unauthorized access or social engineering attacks.
Although full cross-site scripting exploitation and direct information disclosure are prevented by existing input validation and Content Security Policy, the presence of this vulnerability could still pose compliance challenges by potentially exposing users to phishing attacks.
Organizations subject to standards like GDPR or HIPAA, which require protection of personal data and secure access controls, might find this vulnerability relevant as it could indirectly impact data security and user trust.
Mitigation steps such as upgrading to version 26.1.0 or later, restricting access via internal firewall rules, auditing administrative accounts, and reviewing stored identities are recommended to reduce risk and support compliance efforts.
Can you explain this vulnerability to me?
This vulnerability is a Stored HTML Injection found in the Credentials Manager feature of Guardian/CMC software versions before 26.1.0. It occurs because the system does not properly validate input parameters, allowing an authenticated administrator to insert malicious HTML tags into an identity definition.
When another user tries to delete this compromised identity, the injected HTML executes in their browser. This can lead to phishing attacks or open redirect exploits. However, full cross-site scripting (XSS) attacks and direct data disclosure are prevented by existing input validation and Content Security Policy settings.
How can this vulnerability impact me? :
The vulnerability can impact you by enabling phishing attacks or open redirect exploits when a user deletes a maliciously crafted identity. This could trick users into revealing sensitive information or redirect them to malicious websites.
Although the risk is medium and full XSS exploitation or direct information disclosure is mitigated, the presence of malicious HTML execution in a user's browser can still compromise user trust and security.
To mitigate this risk, it is recommended to upgrade to version 26.1.0 or later, restrict access to the web management interface using internal firewall rules, audit administrative accounts, and review stored identities in the Credentials Manager.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by auditing the stored identities in the Credentials Manager for any malicious HTML tags injected by authenticated administrators.
Additionally, reviewing administrative accounts for suspicious activity and access patterns can help identify potential exploitation attempts.
Since the vulnerability involves injected HTML in identity definitions, commands or scripts that extract and search for HTML tags within stored identities could be used.
- Use web management interface logs or export stored identities and grep for suspicious HTML tags such as <script>, <iframe>, or other HTML elements.
- Audit administrative user actions and check for recent changes to identities that might contain injected HTML.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading the Guardian/CMC software to version 26.1.0 or later, where this vulnerability is resolved.
Restrict access to the web management interface by implementing internal firewall rules to limit administrative access.
Audit administrative accounts to ensure only authorized users have access and review stored identities in the Credentials Manager for any malicious HTML injections.