Skip to main content
HighCodeOWASP A01:2021CWE-601

How to fix: location.replace(userInput)

location.replace(userUrl) navigates the current page to the attacker-supplied URL while removing the original entry from history. The open-redirect impact is identical to window.location but harder for the victim to back out of.

Why it matters

Phishing campaigns can replace the legitimate history entry, making the back button useless.

The `code-redirect-location-replace` check verifies that the server does not expose the `redirect-location-replace` 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. 1Validate the destination host against a strict allowlist.
  2. 2Use URL parsing to extract and compare origins.
  3. 3Log all redirect destinations for audit.

Code examples

Validate before location.replace

TypeScript
function safeReplace(url: string) {
  const parsed = new URL(url, window.location.origin);
  if (!["http:", "https:"].includes(parsed.protocol)) {
    throw new Error("Unsafe redirect");
  }
  window.location.replace(parsed.href);
}

References

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

See every code check

Questions

How severe is location.replace(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-location-replace, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does location.replace(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 location.replace(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: location.replace(userInput) | VulnRadar