How to fix: CSP Uses Wildcard Source
Content Security Policy uses wildcard (*) as a source.
Why it matters
Any origin can serve content, defeating CSP protections.
Wildcard sources allow loading resources from any origin.
How to fix it
- 1Replace * with specific trusted domains.
Code examples
Replace CSP wildcards with specific origins
// BAD: script-src *, allows any origin to run scripts
// GOOD: explicit allowlist
export default {
async headers() {
return [{ source: "/(.*)", headers: [{
key: "Content-Security-Policy",
value: "default-src 'self'; script-src 'self' https://cdn.example.com; img-src 'self' data:; object-src 'none';"
}]}];
},
};References
Detected automatically by VulnRadar. The check id is csp-wildcard-source, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Uses Wildcard Source?
- 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-wildcard-source, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP Uses Wildcard Source 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.