Skip to main content
MediumHeadersOWASP A05:2021CWE-693

How to fix: CSP Report-Only Without Enforcement

CSP-Report-Only is set but no enforcing CSP header exists.

Why it matters

The site is logging CSP violations but not actually blocking them.

CSP-Report-Only is meant for testing before deployment. Running it without an enforcing CSP means zero protection.

How to fix it

  1. 1Deploy an enforcing Content-Security-Policy header alongside report-only.
  2. 2Start with a restrictive policy and relax based on report-only findings.

Code examples

Both headers

text
Content-Security-Policy: default-src 'self'; script-src 'self'
Content-Security-Policy-Report-Only: default-src 'self'; report-uri /csp-report

References

Detected automatically by VulnRadar. The check id is csp-report-only, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is CSP Report-Only Without Enforcement?
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 csp-report-only, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does CSP Report-Only Without Enforcement 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 csp report-only without enforcement

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: CSP Report-Only Without Enforcement | VulnRadar