How to fix: CSP Allows unsafe-inline Scripts
CSP script-src permits inline scripts without nonce or hash.
Why it matters
Inline scripts negate most XSS protections CSP provides.
unsafe-inline without nonce/hash allows any inline script to execute.
How to fix it
- 1Use nonce-based or hash-based CSP instead of unsafe-inline.
Code examples
Replace unsafe-inline with nonces
import { randomBytes } from "crypto";
// Generate nonce per request
const nonce = randomBytes(16).toString("base64");
// Set CSP header
res.setHeader("Content-Security-Policy",
`script-src 'nonce-${nonce}' 'strict-dynamic'; object-src 'none';`
);
// In HTML: <script nonce="{nonce}">...</script>References
Detected automatically by VulnRadar. The check id is csp-unsafe-inline-script, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Allows unsafe-inline Scripts?
- VulnRadar rates this high severity in the headers 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 csp-unsafe-inline-script, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP Allows unsafe-inline Scripts map to?
- It maps to CWE-693. In the OWASP Top 10 it falls under A05: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.