How to fix: CORS Allow-Headers Wildcard
ACA-Headers: * lets any browser send any header. Restrict to the headers you actually use.
Why it matters
Replace * with an explicit allowlist
ACA-Headers: * lets any browser send any header. Restrict to the headers you actually use.
How to fix it
- 1Replace * with an explicit allowlist
Code examples
Restrict Access-Control-Allow-Headers to specific headers
// BAD: Access-Control-Allow-Headers: *, allows any header from any origin
// GOOD: explicit list
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Access-Control-Allow-Headers", value: "Content-Type, Authorization, X-Requested-With" }] }];
},
};References
Detected automatically by VulnRadar. The check id is access-control-allow-headers-wildcard, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CORS Allow-Headers Wildcard?
- 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 access-control-allow-headers-wildcard, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CORS Allow-Headers Wildcard map to?
- It maps to CWE-942. 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.