web-open-redirect
Open redirect — abuse a redirect param to send users to attacker sites, and chain it (OAuth token theft, SSRF filter bypass, phishing). Load on params like redirect=, next=, url=, return=, callback=, dest=, or a 30x Location built from input. Signals: `?returnUrl=`, login redirects, OAuth `redirect_
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/web-open-redirectWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package87beae6d…0c962d23
87beae6db096…1d2b0c962d231 file · 1.2 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-open-redirect@ee0e0c5
On this page
When it applies
The app redirects to a location derived from user input without validating it stays on-site. Low severity alone — but a powerful chain link.
Why it works
The redirect target is attacker-controlled and trusted. On its own it's phishing; chained, it turns other flows malicious (OAuth codes/tokens sent to your host, SSRF allowlist bypass via a redirect to an internal URL).
Method
- Find the param (
redirect/next/url/return/dest/callback) and set it to an external URL; follow the response — a 30xLocation: https://evil.com(or JS/meta redirect) confirms. - Bypass naive validation:
//evil.com,https:evil.com,https://[email protected],https://target.com.evil.com,/\evil.com, whitelisted-prefix tricks, double-encoding, CRLF. - Chain for impact:
- OAuth: if it's the
redirect_uri/return in an auth flow → steal the code/token (→web-oauth, ATO). - SSRF allowlist: allowed host that open-redirects to an internal target bypasses the filter.
- XSS:
javascript:scheme in the redirect where the sink allows it.
- OAuth: if it's the
Gotchas
- Standalone open redirect is often low/informational — lead with the chain (OAuth/SSRF) for real severity.
- Test both server 30x and client-side (JS
location, meta refresh) redirects. - Path-relative allowlists frequently miss
//and\— try them.
Verify success
The app redirects the user to an attacker-controlled origin, or (chained) a token/code is delivered to your host / an SSRF filter is bypassed.
References
PortSwigger OAuth+redirect labs; OWASP Unvalidated Redirects Cheat Sheet.
Files in this version
- SKILL.md2.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 87beae6d | Signed | – |
More from NoorQureshi
All from this publisherMore in Web and bug bounty
See the category- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login