How to fix: CSP Allows unsafe-eval
Content Security Policy permits eval().
Why it matters
eval() can execute attacker-injected strings as code.
unsafe-eval allows dynamic code execution via eval() and Function().
How to fix it
- 1Remove unsafe-eval and refactor code to avoid eval().
Code examples
Remove unsafe-eval from CSP
// BAD: script-src 'unsafe-eval', enables eval(), Function(), setTimeout(string)
// GOOD: use 'strict-dynamic' with nonces instead
// In Next.js:
export default {
async headers() {
return [{ source: "/(.*)", headers: [{
key: "Content-Security-Policy",
value: "script-src 'self' 'nonce-RANDOM'; object-src 'none';"
}]}];
},
};References
Detected automatically by VulnRadar. The check id is csp-unsafe-eval-detected, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Allows unsafe-eval?
- 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-eval-detected, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP Allows unsafe-eval 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.