hunt-cors

Validate CORS misconfigurations for unauthorized credentialed access to sensitive data.

3|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill hunt-cors-entrovyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-cors
Source: https://github.com/EntroVyx/hermes-agent-offsec/tree/main/skills/offsec/redteam/hunt-cors
Command: npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill hunt-cors-entrovyx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the difficulty of distinguishing between theoretical CORS misconfigurations and actual, high-impact security vulnerabilities that allow unauthorized credentialed data access.

Core Features & Use Cases

  • Vulnerability Validation: Provides a rigorous methodology to confirm if a CORS misconfiguration is exploitable via browser-based proof-of-concepts.
  • Attack Surface Analysis: Guides the identification of sensitive API endpoints and the testing of various bypass techniques like null-origin trust and regex flaws.
  • Use Case: Use this skill to audit an authenticated API endpoint that reflects the Origin header, ensuring you can prove the ability to read sensitive user data before submitting a report.

Quick Start

Use the hunt-cors skill to probe the target API endpoints for credentialed origin reflection and generate a browser-based proof-of-concept.

Frequently Asked Questions about hunt-cors

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

FAQPage Schema
How do I validate CORS misconfigurations for credentialed access?

To validate CORS misconfigurations, systematically verify origin reflection, credential handling, and browser-enforced security policies on authenticated API endpoints. This confirms whether a misconfiguration actually permits unauthorized credentialed access to sensitive data.

What is the difference between a theoretical CORS vulnerability and an exploitable one?

An exploitable CORS vulnerability differs from a theoretical one by confirming unauthorized credentialed access to sensitive data. This requires systematic verification of origin reflection, credential handling, and browser-enforced security policies to prove exploitability via browser-based proof-of-concepts.

How do I test null-origin trust and regex flaws during CORS pentesting?

To test null-origin trust and regex flaws during CORS pentesting, apply attack surface analysis to identify sensitive API endpoints. Probe these authenticated interfaces with various bypass techniques to verify if browser-enforced security policies permit unauthorized credentialed access.

Can I use this to audit authenticated API endpoints for origin reflection?

Yes, you can audit authenticated API endpoints for origin reflection. The methodology guides systematic verification of credential handling and browser-enforced security policies to confirm exploitability and generate a browser-based proof-of-concept for sensitive data access.

What's the best way to prove unauthorized data access via CORS misconfiguration?

The best way to prove unauthorized data access via CORS misconfiguration is generating a browser-based proof-of-concept. This validates that reflected origins and credential handling bypass browser-enforced security policies to permit reading sensitive user data.