CVE-2025-40900: Angular template injection in Reports in Guardian/CMC before 26.1.0
An Angular template injection vulnerability was discovered in the Reports functionality due to improper validation of an input parameter. An authenticated user with report privileges can define a malicious report containing an Angular template payload, or a victim can be socially engineered to import a malicious report template. When the victim views or imports the report, the Angular template executes in their browser context, allowing the attacker to modify application data, or disrupt application availability. Full XSS exploitation and direct information disclosure are prevented by the existing input validation and Content Security Policy configuration.
Security readout for executives and security teams
Plain-English summary
An authenticated report user can create a harmful report, or persuade another user to import one. Opening or importing it can run Angular template content in the victim’s browser, potentially changing application data or disrupting service. Existing validation and Content Security Policy reportedly prevent full cross-site scripting and direct information disclosure.
Executive priority
Schedule remediation through normal vulnerability-management timelines, prioritizing systems with many report users or weak privilege controls. Escalate if suspicious report imports, unauthorized data changes, or availability disruptions are found. Current evidence supports moderate urgency rather than an emergency response.
Technical view
CVE-2025-40900 is a CWE-1336 Angular template injection in Nozomi Networks Guardian and CMC Reports. Improper parameter validation permits browser-context template execution after a privileged user creates a report or a victim imports one. It has CVSS 4.0 score 5.1; confidentiality impact is rated none, while integrity and availability impacts are low.
Likely exposure
Exposure is limited to Guardian or CMC deployments before 26.1.0 where users can define reports or import untrusted report templates. Authentication, report privileges, or victim interaction are required. The bundle’s structured affected-version entries are inconclusive, so confirm exact applicability against the vendor advisories.
Exploitation context
The supplied evidence does not establish active exploitation, and the CVE is not identified as KEV. Exploitation requires a report-privileged account or social engineering that convinces a victim to import a malicious template. Existing validation and CSP constrain the reported impact.
Researcher notes
The reported vector is CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Full XSS and direct disclosure are reportedly blocked. The title defines affected releases as before 26.1.0, but the structured affected entries list version “0” with default unaffected; consult vendor advisories for authoritative version mapping.
Mitigation direction
Upgrade Guardian and CMC installations before 26.1.0 to version 26.1.0 or later, subject to vendor guidance.
Restrict report creation and import privileges to trusted, necessary accounts.
Do not import report templates from untrusted or unverified sources.
Review the Nozomi and Siemens advisories for product-specific remediation requirements.
Validation and detection
Inventory Guardian and CMC versions and identify installations earlier than 26.1.0.
Review which accounts possess report creation or import privileges.
Audit recent report creation, import, and viewing activity for unexpected templates or changes.
Confirm Content Security Policy remains enabled and matches vendor-supported configuration.
Verify the installed version and remediation status against the applicable vendor advisory.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1336: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.