How to fix: Missing Clickjacking Protection
Neither X-Frame-Options nor CSP frame-ancestors directive is set, leaving the site vulnerable to clickjacking.
Why it matters
Attackers can embed your site in a hidden iframe and trick users into clicking on elements they don't intend to.
Clickjacking is an attack where a malicious site embeds your site in a transparent iframe. Users think they're interacting with the visible page but are actually clicking on your site.
How to fix it
- 1Add X-Frame-Options: DENY or SAMEORIGIN to your responses.
- 2Alternatively, use the CSP frame-ancestors directive for more granular control.
- 3DENY prevents all framing; SAMEORIGIN allows framing only from the same origin.
Code examples
Next.js
const nextConfig = {
async headers() {
return [{
source: '/(.*)',
headers: [{ key: 'X-Frame-Options', value: 'DENY' }],
}];
},
};Nginx
add_header X-Frame-Options "DENY" always;Apache
Header always set X-Frame-Options "DENY"Caddy
header X-Frame-Options "DENY"Express (Node.js)
app.use((req, res, next) => {
res.setHeader('X-Frame-Options', 'DENY');
next();
});Deno (Hono)
app.use('*', async (c, next) => {
await next();
c.header('X-Frame-Options', 'DENY');
});Bun (Elysia)
app.onAfterHandle(({ set }) => {
set.headers['X-Frame-Options'] = 'DENY';
});References
Detected automatically by VulnRadar. The check id is clickjack-missing, stable across every scan so you can filter or diff on it.
More headers checks
- HighMissing HTTP Strict Transport Security (HSTS)
- HighMissing Content Security Policy (CSP)
- LowMissing Referrer-Policy Header
- LowMissing Permissions-Policy Header
- MediumWildcard CORS Policy
- LowMissing X-XSS-Protection Header
- MediumDangerous CORS Configuration
- InfoMissing Cross-Origin-Resource-Policy (CORP)
Questions
- How severe is Missing Clickjacking Protection?
- 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 clickjack-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing Clickjacking Protection 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.