How to fix: No Content-Security-Policy enforces Trusted Types
Pages that render user-controlled HTML but lack both a Trusted Types policy and the CSP directive to enforce it leave classic DOM XSS vectors undefended.
Why it matters
Attacker-controlled HTML strings reach innerHTML / insertAdjacentHTML unchecked, enabling stored DOM XSS.
The `code-csp-missing-trusted-types` check verifies that the server does not expose the `csp-missing-trusted-types` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Set CSP: require-trusted-types-for 'script'; trusted-types default.
- 2Register a sanitizing policy (DOMPurify) and use it everywhere.
- 3Subscribe to securitypolicyviolation events to detect leaks.
Code examples
Add Trusted Types directive to CSP
// CSP should include:
// Content-Security-Policy: ...; require-trusted-types-for 'script'; trusted-types default
// This prevents direct string assignment to innerHTML and other XSS sinksReferences
Detected automatically by VulnRadar. The check id is code-csp-missing-trusted-types, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is No Content-Security-Policy enforces Trusted Types?
- VulnRadar rates this medium severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-csp-missing-trusted-types, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does No Content-Security-Policy enforces Trusted Types map to?
- It maps to CWE-79. In the OWASP Top 10 it falls under A03:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.