Auditing CORS Policy

Overview

CORS misconfiguration is one of the most common middle-severity findings in web bug bounties. The browser-enforced rules are subtle, the failure modes are silent (the wrong cors response just works until an attacker weaponizes it), and the "fix" engineers reach for — Access-Control-Allow-Origin: * — opens the very class of attacks CORS was meant to prevent when paired with credentials.

This skill probes each common CORS misconfiguration with synthetic Origin headers and grades the response.

When the skill produces findings

Finding	Severity	Threshold	Affected control
Origin reflected without validation	HIGH	Synthetic Origin https://attacker.example echoed in Allow-Origin	OWASP A05:2021
Allow-Credentials:true with wildcard Allow-Origin	CRITICAL	Browser rejects but server is asserting the worst combo	OWASP A05:2021
Allow-Credentials:true with reflected Origin	CRITICAL	Attacker site can read authenticated responses cross-origin	OWASP A05:2021, CWE-942
Subdomain wildcard pattern bypass	HIGH	Allow-Origin: *.example.com matches attacker.example.com.evil.com	CWE-942
Missing Vary:Origin on per-origin response	MEDIUM	CDN caches one origin's response for all origins	RFC 7234
Preflight cache > 86400s	LOW	Access-Control-Max-Age over 24h limits revocation agility	MDN best practice