Skip to main content
MediumActive probingOWASP A01:2021CWE-601

How to fix: Confirmed Open Redirect

A same-host link or form on this page uses a well-known redirect-parameter name (redirect, next, return_to, and similar), and setting that parameter to an external URL made the endpoint send a 3xx redirect to that exact external URL. This confirms the redirect target is not validated against an allowlist -- unlike the pattern-based 'Potential Open Redirect Parameters' finding, this one was actively verified by making the target actually redirect.

Why it matters

An attacker can craft a link to this site's own domain (which victims and email/spam filters trust) that silently forwards to a phishing page, a malware download, or an OAuth consent-theft page, borrowing the target's trusted domain and reputation.

This is a confirmed, active finding: the scanner only probed a redirect parameter the page itself already discloses using (found in a same-host link or form action), never a guessed endpoint, and observed a live 3xx response whose Location header echoed the canary target back exactly. The active-probing category that produced it is opt-in and off by default, since submitting real requests to a target is a materially different action than reading its responses.

How to fix it

  1. 1Validate any redirect target against an explicit allowlist of permitted paths or domains before issuing a redirect.
  2. 2Prefer relative, same-origin redirect targets (a path, not a full URL) wherever the use case allows it.
  3. 3If redirecting to a partner/third-party domain is a legitimate feature, use an intermediate confirmation page that shows the destination before leaving your site.
  4. 4Re-run this scan after the fix to confirm the endpoint no longer redirects to the canary URL.

Code examples

Allowlist the redirect target

TypeScript
// Bad: redirects wherever the query string says
res.redirect(req.query.next);

// Good: only ever redirect to a known-safe, same-origin path
const ALLOWED = new Set(['/dashboard', '/settings', '/']);
res.redirect(ALLOWED.has(req.query.next) ? req.query.next : '/');

References

Detected automatically by VulnRadar. The check id is confirmed-open-redirect, stable across every scan so you can filter or diff on it.

See every active probing check

Questions

How severe is Confirmed Open Redirect?
VulnRadar rates this medium severity in the active probing category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id confirmed-open-redirect, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Confirmed Open Redirect map to?
It maps to CWE-601. In the OWASP Top 10 it falls under A01:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for confirmed open redirect

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Confirmed Open Redirect | VulnRadar