How to fix: Missing X-Frame-Options / frame-ancestors CSP
Pages without X-Frame-Options: DENY (or a CSP frame-ancestors 'none') can be embedded inside an attacker-controlled iframe, enabling clickjacking against authenticated users.
Why it matters
Attacker overlays a transparent iframe on a decoy page; clicks land on the victim's session, performing unintended actions.
The `code-clickjack-x-frame-options` check verifies that the server does not expose the `clickjack-x-frame-options` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Send X-Frame-Options: DENY (or SAMEORIGIN if same-origin framing is required).
- 2Set Content-Security-Policy: frame-ancestors 'none' (or 'self').
- 3Combine with SameSite=Lax cookies to reduce cross-site risk.
Code examples
Add X-Frame-Options or CSP frame-ancestors
// Prevent your site from being embedded in iframes
res.setHeader("X-Frame-Options", "DENY");
// Or use CSP frame-ancestors (more flexible):
res.setHeader("Content-Security-Policy", "frame-ancestors 'none';");References
Detected automatically by VulnRadar. The check id is code-clickjack-x-frame-options, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Missing X-Frame-Options / frame-ancestors CSP?
- VulnRadar rates this medium severity in the code 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 code-clickjack-x-frame-options, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing X-Frame-Options / frame-ancestors CSP 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.