hunt-open-redirect

Detects and exploits open redirect vulnerabilities including OAuth redirect_uri bypass chains.

6|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Wyl-cmd/kxns-cli --skill hunt-open-redirect-wyl-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-open-redirect
Source: https://github.com/Wyl-cmd/kxns-cli/tree/main/src/kxns_cli/skills/hunt-open-redirect
Command: npx skills add https://github.com/Wyl-cmd/kxns-cli --skill hunt-open-redirect-wyl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open redirect vulnerabilities are often dismissed as low-severity findings, yet they become critical when chained to OAuth token theft, phishing, or SSRF. This Skill provides a systematic methodology to discover redirect parameters, bypass validation filters, and escalate low-impact redirects into account-takeover chains. ## Core Features & Use Cases - Redirect Parameter Discovery: Enumerate redirect-controlling parameters (?url=, ?next=, ?redirect_uri=, ?returnTo=) across login, logout, OAuth, and payment flows using gf patterns and grep. - Bypass Payload Library: Apply a curated bypass table covering protocol-relative URLs, backslash tricks, at-sign confusion, null bytes, whitespace injection, and javascript:/data: URIs. - Chain Escalation: Pivot open redirects into OAuth auth-code theft (ATO), server-side SSRF, session fixation, and CSRF Referer bypass. - Use Case: During a bug bounty engagement, you find an OAuth authorize endpoint. Use this Skill to test whether redirect_uri accepts an open redirect on a trusted domain, capture the victim's auth code, and demonstrate full account takeover. ## Quick Start Ask the agent to hunt for open redirect vulnerabilities on the target domain, enumerate redirect parameters, test bypass payloads, and check whether any redirect can be chained into the OAuth redirect_uri flow.

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?

Enumerate redirect-controlling parameters like ?url=, ?next=, ?redirect=, and ?returnTo= from crawled URLs using gf redirect patterns, then replace values with an attacker-controlled domain via qsreplace and check whether the response Location header points to your domain.

How to bypass open redirect URL validation filters?

Common bypasses include protocol-relative URLs (//evil.com), backslash tricks (/\\evil.com), at-sign confusion ([email protected]), null bytes, tab/newline injection, and javascript: or data: URIs. The bypass table maps each validation type to a working payload.

Can an open redirect lead to account takeover?

Yes. When an OAuth authorization endpoint accepts a redirect_uri containing an open redirect on a trusted domain, the victim's authorization code is sent to the attacker's host and exchanged for an access token, resulting in full account takeover.

What tools automate open redirect detection?

openredirex tests candidate URLs against a payload list, nuclei runs redirect templates at medium/high severity, and the gf plus qsreplace pipeline with curl checks Location headers across large URL sets.

Why is a standalone open redirect usually rated low severity?

A redirect alone only sends users to another site, which most bug bounty programs classify as Low. Severity rises to High or Critical only when chained to OAuth code theft, SSRF via server-side redirect following, or session fixation.

When does an open redirect become an SSRF vulnerability?

When the application follows the redirect server-side, such as in image proxies or link preview fetchers, the attacker-controlled 302 can pivot the server to internal targets like http://169.254.169.254/latest/meta-data/ to steal cloud credentials.