How to fix: CSP Missing frame-src Directive
CSP lacks frame-src directive for iframe sources.
Why it matters
Any content can be loaded in iframes.
frame-src controls which origins can be loaded in frames.
How to fix it
- 1Add frame-src 'self' or 'none' to CSP.
Code examples
Add frame-src to CSP
// Without frame-src, child-src or default-src controls iframe sources
// Be explicit about which origins can be embedded:
export default {
async headers() {
return [{ source: "/(.*)", headers: [{
key: "Content-Security-Policy",
value: "default-src 'self'; frame-src 'self' https://www.youtube.com https://player.vimeo.com; object-src 'none';"
}]}];
},
};References
Detected automatically by VulnRadar. The check id is csp-frame-src-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Missing frame-src Directive?
- VulnRadar rates this low 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-frame-src-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP Missing frame-src Directive 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.