open-redirect

Identify open redirect vulnerabilities by mapping user-controlled parameters to redirect sinks.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/lNwNl/Methodos --skill open-redirect-lnwnl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-redirect
Source: https://github.com/lNwNl/Methodos/tree/main/docker/opencode/skills/open-redirect
Command: npx skills add https://github.com/lNwNl/Methodos --skill open-redirect-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify and validate open redirect vulnerabilities where an application redirects users to attacker-controlled destinations derived from user input, enabling phishing, token theft, and SSRF.

Core Features & Use Cases

  • Redirect discovery: Pinpoints URL parameters and common redirect sinks in both server and JavaScript contexts (e.g., Location headers, res.redirect, window.location).
  • Filter bypass playbook: Tests practical bypasses for typical allowlist and validation logic (protocol-relative URLs, userinfo tricks, encoding/double-decoding, parser confusion).
  • Chain exploitation guidance: Maps open redirect into high-impact multi-step scenarios including phishing amplification, OAuth token/code theft, CSRF referer bypass, and SSRF via redirect-following.

Quick Start

Ask an AI to produce a targeted open redirect test plan for your application, including the exact parameter names to try, the relevant redirect sinks to inspect, and specific bypass payloads to validate.

Frequently Asked Questions about open-redirect

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

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

Find open redirect vulnerabilities by mapping user-controlled URL parameters to redirect sinks like Location headers or window.location, then validating browser and server redirect behavior. Test common parameters and inspect both server-side and JavaScript DOM-based redirect flows.

What are common open redirect filter bypass payloads?

Common open redirect filter bypass payloads include protocol-relative URLs, userinfo tricks, URL encoding and double-decoding, and parser confusion techniques. These bypasses exploit differences in how validation logic and browsers parse destination URLs.

Can an open redirect lead to OAuth token theft?

An open redirect can lead to OAuth token theft by manipulating the redirect_uri parameter to intercept authorization codes or tokens. Exploit chains map redirect flaws into high-impact scenarios including phishing amplification and OAuth/OIDC code theft.

How does an open redirect vulnerability cause SSRF?

An open redirect causes SSRF when server-side components like fetchers or link previews follow the redirect to an attacker-controlled internal destination. Testing redirect-following behavior validates whether server-side request forgery outcomes are possible.

What is a DOM-based open redirect and how is it tested?

A DOM-based open redirect occurs when client-side JavaScript assigns user input to redirect sinks like window.location. Test by injecting payload variations into client-side parameters and observing browser navigation behavior under different parsing rules.

How do I bypass referer-based CSRF defenses using an open redirect?

Bypass referer-based CSRF defenses by chaining an open redirect to ensure the malicious request originates from a trusted domain, preserving the expected Referer header. Validate redirect behavior to confirm the defense-dependency on Referer is exploitable.