Skip to main content
MediumCodeOWASP A03:2021CWE-79

How to fix: No Trusted Types policy created

Pages that write to innerHTML, document.write, or eval without first creating a trustedTypes policy leave every string-to-DOM sink undefended. Trusted Types forces a sanitizing policy to gate these sinks.

Why it matters

DOM XSS via injected strings cannot be blocked without Trusted Types enforcement.

The `code-csp-no-trusted-types` check verifies that the server does not expose the `csp-no-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

  1. 1Create a default policy: trustedTypes.createPolicy('default', { createHTML: s => DOMPurify.sanitize(s) }).
  2. 2Add require-trusted-types-for 'script' to your CSP header.
  3. 3Replace direct innerHTML writes with policy.createHTML(userInput).

Code examples

Add Trusted Types to CSP

TypeScript
// Add require-trusted-types-for to your CSP
// next.config.mjs:
headers: [{ key: "Content-Security-Policy",
  value: "default-src 'self'; require-trusted-types-for 'script';" }]

// Then define a Trusted Types policy:
const policy = trustedTypes.createPolicy("default", {
  createHTML: (s) => DOMPurify.sanitize(s),
  createScript: (s) => { throw new Error("Scripts must be static"); },
  createScriptURL: (url) => {
    if (new URL(url).origin !== location.origin) throw new Error("Cross-origin script");
    return url;
  },
});

References

Detected automatically by VulnRadar. The check id is code-csp-no-trustedtypes, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is No Trusted Types policy created?
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-no-trustedtypes, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does No Trusted Types policy created 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.

Propose a checkHow a check is built

Scan your own site for no trusted types policy created

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: No Trusted Types policy created | VulnRadar