hunt-cors

Detect and validate exploitable CORS misconfigurations on web applications and APIs.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-cors-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-cors
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/skills/bughunter/hunt-cors
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-cors-inventashif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers often report CORS findings that browsers would actually block, producing false positives and rejected bug bounty reports. This Skill provides a rigorous methodology to identify genuinely exploitable CORS misconfigurations and prove impact with browser-based evidence. ## Core Features & Use Cases - Origin Reflection Testing: Systematically probe endpoints for reflect-any-origin, null-origin trust, and trusted insecure HTTP origins with credentials. - Regex Bypass Classification: Match subdomain trust-regex flaws (unescaped dot, missing end-anchor, prefix-only) to the correct bypass payload instead of guessing. - Browser Proof-of-Concept Validation: Use fetch-based and sandboxed-iframe PoCs to confirm a credentialed cross-origin read actually succeeds, since curl ignores CORS enforcement. - Use Case: While testing a target's /api/me endpoint, you see the Origin header reflected with Access-Control-Allow-Credentials: true. Use this Skill to build a hosted browser PoC that reads the authenticated response body from an attacker-controlled origin, then exfiltrate it to an OOB listener as unambiguous proof for a High-severity report. ## Quick Start Test the target's API endpoints for CORS misconfigurations and build a browser proof-of-concept for any origin reflection with credentials you find.

Frequently Asked Questions about hunt-cors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for CORS misconfiguration on a website?

Send requests with an attacker-controlled Origin header and check whether the server reflects it in Access-Control-Allow-Origin alongside Access-Control-Allow-Credentials: true. Then confirm the credentialed cross-origin read in a real browser, since curl does not enforce CORS.

How to bypass CORS subdomain regex filters?

First identify the regex flaw class: missing end-anchor allows target.com.evil.com, a missing escaped dot allows eviltarget.com, and unescaped dots match any character. Send the payload matching the specific flaw and check whether your registerable origin is reflected with credentials allowed.

Is Access-Control-Allow-Origin wildcard with credentials exploitable?

No. Browsers refuse to expose responses when ACAO is * on a credentialed request, so wildcard-only endpoints are not credential-exploitable. They only matter if the data served is sensitive without any session, which is usually Low or Informational severity.

Why does my CORS finding get rejected as a false positive?

Most rejections happen because curl shows a reflected header but a browser would block the read. A valid High requires a browser proof-of-concept showing the authenticated response body is readable from an attacker-controlled origin, plus sensitive data in that body.

Can a null origin be used to exploit CORS?

Yes, if the server returns Access-Control-Allow-Origin: null with credentials allowed. A sandboxed iframe without allow-same-origin emits Origin: null, letting any page read authenticated cross-origin data, which is typically Medium to High severity when browser-proven.

What tools automate CORS misconfiguration scanning?

Corsy performs fast reflection, null-origin, and pre-domain checks, and nuclei has CORS misconfiguration templates. Treat every automated hit as a lead only, and always re-confirm exploitability with a browser-based proof-of-concept before reporting.