How to fix: CSP Contains Framework-Required Directives
The CSP includes directives required by the frontend framework. This is expected for Next.js, React, Vue, or Angular applications.
Why it matters
Framework-required directives slightly reduce XSS protection, but are necessary for the framework to function.
Modern frameworks require 'unsafe-inline' and/or 'unsafe-eval' for their runtime features. While these weaken CSP, they're necessary trade-offs.
How to fix it
- 1Ensure all user input is properly sanitized.
- 2Keep framework and dependencies up to date.
- 3Use strict CSP for other directives.
- 4Consider strict-dynamic with nonces.
Code examples
Next.js CSP
const csp = [
"default-src 'self'",
"script-src 'self' 'unsafe-inline' 'unsafe-eval'",
"style-src 'self' 'unsafe-inline'",
"frame-ancestors 'none'",
"base-uri 'self'",
].join('; ');References
Detected automatically by VulnRadar. The check id is csp-framework-required, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Contains Framework-Required Directives?
- VulnRadar rates this info 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-framework-required, which stays the same between runs so you can filter, diff, or gate CI on it.
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.