hunt-cors

Detect CORS misconfigurations enabling credentialed cross-origin reads of authenticated data.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill hunt-cors-uphiago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-cors
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/hunt-cors
Command: npx skills add https://github.com/uphiago/recon-skills --skill hunt-cors-uphiago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical gap of undetected CORS misconfigurations in web applications and APIs that allow attackers to steal sensitive authenticated user data, including PII, session tokens, and CSRF tokens, which are often missed in standard reconnaissance workflows.

Core Features & Use Cases

  • Comprehensive Flaw Coverage: Detects all major CORS misconfiguration classes including origin reflection with credentials, null-origin trust, subdomain regex bypasses, pre-flight gating bypasses, and loose postMessage origin checks.
  • Field-Validated Methodology: Includes step-by-step hunting workflows, regex bypass payload tables tailored to specific server parsing flaws, and browser-based proof-of-concept templates proven on real-world targets.
  • Use Case: For a pentester testing a WordPress e-commerce site, use this skill to systematically probe REST API endpoints for CORS credential reflection, confirm the vulnerability with a browser PoC, and chain the finding to token theft for account takeover.

Quick Start

Use the hunt-cors skill to test all identified API endpoints on the target web application for CORS misconfigurations, confirm any findings with a browser-based proof of concept, and document the impact of any authenticated data exfiltration risk.

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 misconfigurations that allow credentialed cross-origin data theft?

To test for CORS misconfigurations, probe API endpoints for origin reflection with credentials, null-origin trust, and subdomain regex bypasses. You validate authenticated data exfiltration risks using browser-based proof-of-concept templates.

What types of CORS vulnerabilities should I look for during a red team engagement?

During a red team engagement, hunt for CORS vulnerabilities including origin reflection with credentials, null-origin trust, subdomain regex bypasses, pre-flight gating bypasses, and loose postMessage origin checks exposing sensitive data theft.

Can I use this CORS hunting methodology on single-page applications and WordPress REST APIs?

Yes, you can use this CORS hunting methodology on single-page applications, WordPress instances, REST APIs, and any web service emitting Access-Control-Allow-* HTTP response headers to discover high-severity security findings.

How do I bypass CORS regex whitelists when testing API security?

To bypass CORS regex whitelists, apply context-aware regex bypass payload selection tailored to specific server parsing flaws. This systematically tests trust boundaries against malformed origins and subdomain variations during API security testing.

What is the best way to generate a browser-based proof of concept for a CORS flaw?

The best way to generate a browser-based proof of concept for a CORS flaw is using field-validated templates that confirm the vulnerability by executing credentialed cross-origin reads of authenticated user data from the targeted web application.