hunt-csrf

Detect modern CSRF vulnerabilities including SameSite bypasses and OAuth RelayState flaws.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard CSRF testing only catches basic missing token flaws, missing modern bypasses like SameSite misconfigurations, JSON CSRF via text/plain enctype, OAuth RelayState validation gaps, and chain-to-account-takeover patterns that lead to high-severity, high-payout bug bounty findings.

Core Features & Use Cases

  • Modern Bypass Detection: Covers SameSite=Lax sibling subdomain bypasses, JSON CSRF via Content-Type abuse, OAuth/SAML RelayState flaws, and framework misconfigurations like disabled CSRF middleware.
  • Crown Jewel Target Prioritization: Focuses on high-impact flows including OAuth/SSO account linking, email change endpoints, third-party dashboards (Grafana), and social platform integrations that chain directly to full account takeover.
  • Field-Validated Methodology: Built from 15 real bug bounty reports including $10k GitHub Enterprise and $5k Stripe Dashboard findings, with step-by-step hunting checks, browser-compatible PoC templates, and impact validation gates.

Quick Start

Use the hunt-csrf skill to test all state-changing endpoints on your authorized target for CSRF vulnerabilities, prioritize OAuth and account linking flows, and validate any findings with a browser-compatible proof of concept that demonstrates concrete account takeover impact.

Frequently Asked Questions about hunt-csrf

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

FAQPage Schema
How do I find SameSite bypass and JSON CSRF vulnerabilities that automated scanners miss?

To find SameSite bypass and JSON CSRF vulnerabilities, test state-changing endpoints for SameSite=Lax sibling subdomain bypasses and Content-Type abuse using text/plain enctype. This approach detects modern CSRF flaws that standard automated scanners overlook during penetration testing.

What is an OAuth RelayState CSRF flaw and how does it lead to account takeover?

An OAuth RelayState CSRF flaw is a validation gap in OAuth/SAML flows allowing attackers to hijack the RelayState parameter. This misconfiguration chains directly to full account takeover by forcing victims to link attacker-controlled OAuth/SSO accounts during authorized security assessments.

Can I use CSRF testing techniques to target third-party dashboards like Grafana?

Yes, you can target third-party dashboards like Grafana for CSRF testing. Prioritize high-impact flows including OAuth/SSO account linking, email change endpoints, and social platform integrations within these dashboards to chain findings directly to full account takeover.

How do I validate a CSRF bug bounty finding with a browser-compatible proof of concept?

To validate a CSRF bug bounty finding, use browser-compatible proof of concept templates that demonstrate concrete account takeover impact. Apply field-validated detection patterns and impact validation gates aligned with real disclosed reports like GitHub Enterprise and Stripe Dashboard findings.

Why does standard CSRF testing fail to detect modern web security vulnerabilities?

Standard CSRF testing fails to detect modern web security vulnerabilities because it only catches basic missing token flaws. It misses SameSite misconfigurations, JSON CSRF via text/plain enctype, OAuth RelayState validation gaps, and framework misconfigurations like disabled CSRF middleware.