How to fix: CSP Missing base-uri Directive
The CSP header exists but does not contain a base-uri directive.
Why it matters
An attacker who injects a <base> tag can redirect all relative URLs to their server.
Without base-uri, injected <base> tags can hijack relative resource loading.
How to fix it
- 1Add 'base-uri self' to your CSP.
Code examples
CSP
Content-Security-Policy: ... base-uri 'self';References
Detected automatically by VulnRadar. The check id is csp-base-uri-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Missing base-uri Directive?
- 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-base-uri-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP Missing base-uri Directive 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.