How to fix: CSP Uses Deprecated report-uri
CSP uses the deprecated 'report-uri' directive without the modern 'report-to' directive.
Why it matters
report-uri is deprecated and may be removed from browsers. Your CSP violation reports may stop working.
The report-to directive replaces report-uri and integrates with the Reporting API. It supports features like report batching and is the future standard.
How to fix it
- 1Add report-to directive alongside report-uri for backward compatibility.
- 2Configure a Report-To header with your reporting endpoint.
Code examples
Migrate report-uri to report-to
// next.config.mjs: use report-to instead of deprecated report-uri
export default {
async headers() {
return [{ source: "/(.*)", headers: [
{ key: "Report-To", value: JSON.stringify({ group: "csp-endpoint", max_age: 86400, endpoints: [{ url: "https://yoursite.com/api/csp-report" }] }) },
{ key: "Content-Security-Policy", value: "default-src 'self'; report-to csp-endpoint" },
]}];
},
};References
Detected automatically by VulnRadar. The check id is csp-report-uri-deprecated, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Uses Deprecated report-uri?
- VulnRadar rates this info 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-uri-deprecated, which stays the same between runs so you can filter, diff, or gate CI on it.
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.