Skip to main content
MediumClient-sideOWASP A05:2021CWE-693

How to fix: CSP Allows 'unsafe-eval'

The CSP header includes 'unsafe-eval', which permits eval(), Function(), setTimeout(string), and setInterval(string). These functions execute strings as code and are primary targets for XSS attacks.

Why it matters

With 'unsafe-eval', any XSS payload that can reach eval() or Function() will execute arbitrary JavaScript. This is a requirement for some older libraries and bundlers but should be eliminated from modern applications.

'unsafe-eval' is needed by some older code patterns and frameworks (older AngularJS, some Webpack configurations). Modern alternatives exist for all of them.

How to fix it

  1. 1Identify what requires unsafe-eval: run the browser console with a strict CSP to see violations.
  2. 2For AngularJS: upgrade to Angular 2+ or use a JIT-free build.
  3. 3For Webpack: use the 'eval-source-map' devtool only in development, not production.
  4. 4Replace any direct eval() calls with safe alternatives.

Code examples

Webpack production config

JavaScript
module.exports = {
  mode: 'production',
  devtool: 'source-map', // Not 'eval-source-map': does NOT require unsafe-eval
};

References

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

See every client-side check

Questions

How severe is CSP Allows 'unsafe-eval'?
VulnRadar rates this medium severity in the client-side 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-script, 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.

Propose a checkHow a check is built

Scan your own site for csp allows 'unsafe-eval'

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: CSP Allows 'unsafe-eval' | VulnRadar