Skip to main content
LowHeadersOWASP A05:2021CWE-693

How to fix: Missing X-XSS-Protection Header

The X-XSS-Protection header is not set and no Content-Security-Policy is present.

Why it matters

Older browsers that still support the XSS auditor won't have it activated.

While the XSS auditor is deprecated in modern browsers, having protection headers is still recommended.

How to fix it

  1. 1Implement a strong Content-Security-Policy (preferred approach).
  2. 2Set X-XSS-Protection: 0 (to avoid the buggy auditor).
  3. 3Focus on input validation and output encoding.

Code examples

CSP preferred

text
Content-Security-Policy: default-src 'self'; script-src 'self'

References

Detected automatically by VulnRadar. The check id is xxss-protection-missing, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Missing X-XSS-Protection Header?
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 xxss-protection-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Missing X-XSS-Protection Header 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.

Propose a checkHow a check is built

Scan your own site for missing x-xss-protection header

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Missing X-XSS-Protection Header | VulnRadar