How to fix: Missing CSP frame-ancestors Directive
Neither CSP frame-ancestors nor X-Frame-Options header is present.
Why it matters
Attackers can embed your site in an iframe for clickjacking.
CSP frame-ancestors or X-Frame-Options prevents your site from being framed.
How to fix it
- 1Add frame-ancestors 'none' or 'self' to your CSP.
- 2Or add X-Frame-Options: DENY.
- 3CSP frame-ancestors is preferred.
Code examples
CSP
Content-Security-Policy: frame-ancestors 'none';References
Detected automatically by VulnRadar. The check id is csp-frame-ancestors-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Missing CSP frame-ancestors Directive?
- VulnRadar rates this medium 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-ancestors-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing CSP frame-ancestors Directive map to?
- It maps to CWE-1021. 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.