How to fix: X-Frame-Options: ALLOWALL
ALLOWALL (Chromium extension) explicitly disables framing protection. Use CSP frame-ancestors instead.
Why it matters
Remove X-Frame-Options or set DENY/SAMEORIGIN; rely on CSP frame-ancestors for modern browsers
ALLOWALL (Chromium extension) explicitly disables framing protection. Use CSP frame-ancestors instead.
How to fix it
- 1Remove X-Frame-Options or set DENY/SAMEORIGIN; rely on CSP frame-ancestors for modern browsers
Code examples
Set X-Frame-Options to DENY or SAMEORIGIN
// X-Frame-Options: ALLOWALL is not a valid value and is ignored by browsers
// Use one of:
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "X-Frame-Options", value: "DENY" }] }];
},
};
// Or to allow same-origin framing only:
// X-Frame-Options: SAMEORIGIN
// Prefer CSP frame-ancestors which is more flexible:
// Content-Security-Policy: frame-ancestors 'none'References
Detected automatically by VulnRadar. The check id is x-frame-options-allowall, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is X-Frame-Options: ALLOWALL?
- VulnRadar rates this high 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 x-frame-options-allowall, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-Frame-Options: ALLOWALL 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.