01Description
The application redirected users to a URL taken from a request parameter without validating the destination.
02Impact
Attackers can craft links on the trusted domain that send users to a malicious site, making phishing more convincing. In OAuth and single sign-on flows, open redirects can be used to steal authorization codes or tokens.
03Severity
Typically
Low
Typically Low. Low by default. Medium when the redirect is part of an OAuth or SSO flow, where it can leak authorization codes or tokens.
04How to verify
- 1Identify parameters such as next, return, url and redirect.
- 2Supply an external domain and encoded variants and confirm the redirect.
- 3Check whether the redirect participates in authentication flows.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Redirect only to relative paths or an allow-list of destinations.
- 2Map redirect targets to identifiers instead of accepting URLs.
- 3Validate redirect URIs exactly in OAuth client registrations.
Draft findings like this from your own evidence
Book a demo