open-redirect

Identify open redirect flaws in user-controlled navigation inputs.

241|28|Updated May 20, 2026
One-click install
npx skills add https://github.com/ok-helloworld/vibe-pentest --skill open-redirect-ok-helloworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-redirect
Source: https://github.com/ok-helloworld/vibe-pentest/tree/main/references/pentest_skills/open-redirect
Command: npx skills add https://github.com/ok-helloworld/vibe-pentest --skill open-redirect-ok-helloworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Open redirect vulnerabilities let attackers redirect users to attacker-controlled destinations using parameters, undermining trust in legitimate links and enabling multi-stage attacks like phishing, OAuth token theft, and SSRF.

Core Features & Use Cases

  • Redirect Parameter Identification: Map and test common redirect-driving parameters such as url, next, returnUrl, and dest to locate the vulnerable redirect behavior.
  • Sink Coverage Across Contexts: Validate both server-side redirect sinks (e.g., HTTP Location/header-based flows) and client-side JavaScript navigation sinks (e.g., window.location, window.location.href).
  • Filter Bypass Techniques: Use realistic bypass payload patterns including protocol-relative URLs, userinfo delimiter abuse, encoding tricks, and parser confusion to confirm reachability.

Quick Start

Ask an AI agent to use the open-redirect playbook to identify all redirect parameters on a target URL and generate a minimal set of proof-of-concept payloads that demonstrate external redirects safely within the allowed scope.

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 in web applications?

Testing for open redirect vulnerabilities involves mapping and testing common redirect-driving parameters like url, next, returnUrl, and dest to locate navigation behavior to external, attacker-controlled destinations.

What is an open redirect flaw and how does it enable phishing?

An open redirect flaw occurs when user-controlled inputs drive navigation to attacker-controlled destinations, undermining trust in legitimate links and enabling multi-stage attacks like phishing, OAuth token theft, and SSRF.

How do I bypass redirect filters using protocol-relative URLs and encoding tricks?

Bypass redirect filters using realistic payload patterns like protocol-relative URLs, userinfo delimiter abuse, encoding tricks, and parser confusion to confirm external redirect reachability across server-side and client-side contexts.

Does this open redirect playbook cover both server-side and client-side JavaScript sinks?

Yes, this validates both server-side redirect sinks handling HTTP Location headers and client-side JavaScript navigation sinks including window.location and window.location.href across various redirect contexts.

Can I use this to check OAuth redirect_uri chains for token theft risks?

Yes, you can apply the playbook to web endpoints across OAuth redirect_uri chains to expose open redirects that enable token theft and identify vulnerable redirect behavior.