• Exposure

Open Redirect

An open redirect lets attackers supply a destination URL and bounce users through your trusted domain to a malicious site — fuel for phishing and OAuth abuse.

How attackers abuse it

Login and marketing flows often take ?next= or ?url= parameters. Without allowlisting, https://yoursite.com/login?next=https://evil.example looks legitimate in the address bar before the hop.

OAuth and SSO redirect_uri weaknesses are closely related: weak validation lets tokens or codes land on attacker-controlled endpoints.

Open redirects also chain with XSS filters and SSRF bypasses when servers follow or trust “same-site” redirects naively.

What proof looks like

Proof shows a request that results in a 3xx (or meta/JS redirect) to an arbitrary external host under attacker control, using your domain as the trusted first hop.

In PandaONE, this class maps to the Exposure finding category. Alerts ship only with evidence — never as unverified scanner noise.

How to prevent it

  • Allowlist redirect targets; prefer relative paths resolved against a fixed origin.
  • Reject external schemes and protocol-relative URLs in redirect parameters.
  • Strictly validate OAuth redirect_uri against pre-registered values.
  • Log and alert on redirect parameters pointing off-domain.
  • Educate support and marketing teams not to ship unvalidated “exit” links.

• FAQ

Frequently asked questions

← All vulnerability classes

Hunt this class with proof

Or scan your domain.

Featured on ScrollLaunchFeatured on CodeHype