How to fix: X-XSS-Protection Explicitly Disabled
X-XSS-Protection set to 0.
Why it matters
While deprecated, explicitly disabling XSS filter removes a defense layer in older browsers.
Setting X-XSS-Protection to 0 turns off the built-in XSS auditor.
How to fix it
- 1Remove the header entirely or set to 1; mode=block.
Code examples
Remove X-XSS-Protection: 0 and use CSP instead
// X-XSS-Protection is deprecated in modern browsers
// The header X-XSS-Protection: 0 disables the old browser XSS filter
// Replace with a strong Content-Security-Policy instead:
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Content-Security-Policy", value: "default-src 'self'; script-src 'self'; object-src 'none';" }] }];
},
};References
Detected automatically by VulnRadar. The check id is x-xss-protection-disabled, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is X-XSS-Protection Explicitly Disabled?
- 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 x-xss-protection-disabled, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-XSS-Protection Explicitly Disabled 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.