hunt-cors is a skill for Claude covering CORS misconfiguration: origin-reflection with credentials, null-origin trust, subdomain-regex bypass classes, pre-flight gating bypass, and postMessage origin checks. It opens with the two browser rules that kill most false findings: a wildcard Access-Control-Allow-Origin cannot carry credentials, and Access-Control-Allow-Credentials means nothing unless the origin is also reflected and the body is readable by a credentialed cross-origin fetch.
The skill’s regex-bypass section matches each specific parsing flaw (missing dot separator, missing end-anchor, unescaped dot) to the one payload that exploits it, keeping a tester’s payload targeted to the server’s actual flaw. Every High-severity claim requires a real browser proof of concept, since curl does not enforce the same-origin policy a browser does. It is for assets covered by a program or engagement you are authorized to test.
What You Get
- A two-rule screening pass naming exactly when ACAO and ACAC are and are not exploitable for credentialed cross-origin reads
- A regex-bypass table mapping five distinct subdomain-trust parsing flaws to the one payload each one requires
- Browser HTML proof-of-concept templates for reflect-any-origin reads, null-origin reads via a sandboxed iframe, and trusted-subdomain reads
- A pre-flight (OPTIONS) gating test for whether an attacker origin can drive state-changing PUT/DELETE requests with custom headers
- A chain table and validation discipline section tying CORS findings forward into CSRF, XSS and subdomain-takeover chains
Common Use Cases
- Testing whether an API endpoint reflects an arbitrary Origin header with credentials enabled, exposing an authenticated response to any origin
- Identifying which specific subdomain-trust regex flaw a server has and sending the one bypass payload that matches it
- Building a real browser proof of concept to confirm a CORS misconfiguration is exploitable, since curl alone cannot prove a credentialed cross-origin read
What Makes It Unique
Most CORS guidance treats every reflected origin as a finding and every bypass payload as worth trying against every target. This skill names the specific browser rules that make most header-level findings non-exploitable, and its regex-bypass table assigns one correct payload per parsing flaw, giving a tester a direct match for the server’s exact bug. It also states outright that curl output proves nothing about browser-enforced CORS, so every High-severity claim needs a browser-rendered proof.
Under The Hood
The skill is a single SKILL.md of guidance with no bundled scripts. Following it, the agent sends HTTP requests with varied Origin headers to API endpoints to read Access-Control-* response headers, and writes small HTML proof-of-concept files that it opens in a real browser to confirm whether a cross-origin credentialed fetch returns a readable body. Use it only against assets you are authorized to test.