open-redirect

Tests web applications for open redirect vulnerabilities using bypass techniques and exploitation checklists.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/karenrebecag/spec-driven-standards --skill open-redirect-karenrebecag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-redirect
Source: https://github.com/karenrebecag/spec-driven-standards/tree/main/plugins/security/skills/offensive-open-redirect
Command: npx skills add https://github.com/karenrebecag/spec-driven-standards --skill open-redirect-karenrebecag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications often mishandle user-supplied redirect URLs, and manually testing every redirect parameter, encoding variant, and framework-specific endpoint is slow and error-prone. This Skill provides a structured checklist for finding and exploiting open redirect vulnerabilities during authorized security testing. ## Core Features & Use Cases - Redirect Parameter Discovery: Identifies common redirect parameters (redirect, url, next, return_url) and endpoints across authentication flows, OAuth integrations, and URL shorteners. - Bypass Technique Library: Covers domain spoofing, URL/double encoding, protocol confusion (javascript:, data:), path-based bypasses, and special character abuse to defeat validation logic. - Impact Escalation Guidance: Shows how to chain open redirects with phishing, CSRF, XSS, SSRF, and OAuth token theft to demonstrate real impact. - Use Case: During a bug bounty engagement, you find a login page with a ?next= parameter. Use this Skill to systematically test basic payloads, then encoding and domain-spoofing bypasses, and finally document a working proof of concept. ## Quick Start Use the open-redirect skill to test https://target.com/login?next= for open redirect vulnerabilities and suggest bypass payloads.

Frequently Asked Questions about open-redirect

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

FAQPage Schema
How do I test for open redirect vulnerabilities?▼

Identify redirect parameters like url, next, redirect, or return_url, then submit payloads such as absolute URLs (https://attacker.com), protocol-relative URLs (//attacker.com), and encoded variants. Check whether the server responds with a 3xx redirect to the attacker-controlled domain.

What are common open redirect bypass techniques?▼

Common bypasses include domain spoofing (target.com.attacker.com), URL and double encoding, protocol confusion with javascript: or data: schemes, path-based tricks like ////attacker.com, and special character abuse such as target.com@attacker.com.

Which tools detect open redirect vulnerabilities?▼

OWASP ZAP and Burp Suite scan for redirect issues, while OpenRedireX and Gxss specialize in redirect and redirect-based XSS testing. Waybackurls and Param Spider help discover historical redirect endpoints and parameters.

Can open redirects be exploited beyond phishing?▼

Yes. Open redirects can be chained with XSS via javascript: URIs, used for SSRF by redirecting to internal services, and abused in OAuth flows to steal tokens through manipulated redirect_uri parameters.

How do I prevent open redirect vulnerabilities?▼

Validate redirect targets server-side against an allowlist of permitted domains using proper URL parsing, not string matching. Prefer indirect references like numeric IDs mapped to pre-approved URLs, and show a warning page before external redirects.