Skip to main content
HighCodeOWASP A01:2021CWE-601

How to fix: window.location.href = userInput

Assigning window.location.href to a user-supplied URL performs a top-level navigation to the attacker-chosen host, enabling phishing and credential theft via open redirect.

Why it matters

Attacker hosts a convincing phishing page at the destination and uses the open redirect as the launchpad.

The `code-redirect-window-location-href` check verifies that the server does not expose the `redirect-window-location-href` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.

How to fix it

  1. 1Compare the destination origin against an allowlist before assigning.
  2. 2Use URL parsing to extract and validate the host component.
  3. 3Prefer server-issued 302 redirects with allowlisted destinations.

Code examples

Validate URL before setting location.href

TypeScript
function safeNavigate(url: string) {
  const parsed = new URL(url, window.location.origin);
  // Block javascript: and data: schemes
  if (!["http:", "https:"].includes(parsed.protocol)) {
    throw new Error("Unsafe redirect target");
  }
  // Only allow same-origin redirects from user input
  if (parsed.origin !== window.location.origin) {
    throw new Error("Cross-origin redirect not allowed");
  }
  window.location.href = parsed.href;
}

References

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

See every code check

Questions

How severe is window.location.href = userInput?
VulnRadar rates this high severity in the code 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 code-redirect-window-location-href, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does window.location.href = userInput 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 window.location.href = userinput

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: window.location.href = userInput | VulnRadar