hunt-open-redirect

Detects open redirect vulnerabilities and chains them to OAuth token theft and SSRF escalation.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-open-redirect-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-open-redirect
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-open-redirect
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-open-redirect-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open redirect findings are often dismissed as low severity, leaving testers unsure how to demonstrate real impact. This Skill provides a structured methodology to discover redirect parameters, bypass filters, and escalate findings into high-impact chains like OAuth authorization code theft leading to account takeover. ## Core Features & Use Cases - Redirect Parameter Discovery: Enumerates common redirect parameters (next, url, returnTo, callback, redirect_uri) from crawled URLs using gf patterns and grep. - Filter Bypass Payloads: Provides a bypass table covering protocol-relative URLs, backslash tricks, at-sign confusion, URL encoding, null bytes, and JavaScript/data URIs. - Impact Chaining: Maps open redirects to OAuth redirect_uri abuse for auth code theft, phishing with trusted domains, session fixation, and server-side redirect escalation to SSRF. - Use Case: During an authorized bug bounty engagement, you find /logout?returnTo= on the target. Use this Skill to test bypass payloads, confirm the Location header points to your controlled domain, then chain it into the OAuth flow to demonstrate ATO impact. ## Quick Start Use the hunt-open-redirect skill to test the redirect parameters found in my recon output for bypass techniques and OAuth chaining opportunities.

Frequently Asked Questions about hunt-open-redirect

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

FAQPage Schema
How do I find open redirect vulnerabilities in a web application?

Extract URLs containing redirect parameters like next, url, returnTo, dest, and callback from crawled data using gf redirect patterns. Then replace parameter values with a controlled domain and check whether the response Location header points to it.

How to bypass open redirect filters and blacklists?

Common bypasses include protocol-relative URLs (//evil.com), backslash confusion (/\\evil.com), at-sign tricks ([email protected]), URL encoding, null bytes, and subdomain spoofing (target.com.evil.com). Test each payload and inspect the Location header.

Can an open redirect lead to account takeover?

Yes, when chained with OAuth. If the OAuth redirect_uri accepts a URL containing an open redirect on a trusted domain, the authorization code can be sent to an attacker-controlled server, enabling account takeover and raising severity to High or Critical.

What tools automate open redirect detection?

openredirex tests candidate URLs against payload lists, nuclei runs redirect templates at medium and high severity, and gf combined with qsreplace plus curl provides a manual pipeline for checking Location headers on each candidate.

Why is my open redirect report marked as low severity?

A standalone open redirect is typically Low severity because it requires user interaction. To increase impact, chain it to OAuth code theft, phishing with a trusted domain, session fixation, or server-side redirect following that enables SSRF.