How to fix: CORS allows overly broad HTTP methods
Access-Control-Allow-Methods lists methods (e.g., PUT, DELETE, PATCH) that the endpoint does not actually use.
Why it matters
Granting CORS access to methods beyond what is needed enables cross-origin requests to trigger state changes (PUT, DELETE) from malicious sites, combining with CSRF for authenticated destructive actions.
List only the HTTP methods that cross-origin clients actually need to use.
How to fix it
- 1Audit which methods each endpoint supports
- 2Only list those specific methods in Access-Control-Allow-Methods
- 3Return 405 for methods not in your allowlist
Code examples
Minimal CORS methods
return new Response(null, {
headers: {
"Access-Control-Allow-Methods": "GET, POST", // only what you need
"Access-Control-Allow-Origin": "https://partner.yoursite.com",
},
});References
Detected automatically by VulnRadar. The check id is cors-methods-too-permissive, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CORS allows overly broad HTTP methods?
- 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 cors-methods-too-permissive, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CORS allows overly broad HTTP methods 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.