How to fix: top.location / parent.location assignment
top.location = userInput or parent.location.href = userInput navigates the top-most frame from inside an iframe. When the URL is attacker-controlled, it enables clickjacking-aided redirects and breaks frame-busting controls.
Why it matters
Cross-frame navigation to attacker-controlled pages bypasses frame protections and supports phishing chains.
The `code-redirect-top-location` check verifies that the server does not expose the `redirect-top-location` 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
- 1Restrict top-level navigation to same-origin hosts.
- 2Set Content-Security-Policy: frame-ancestors to limit who can frame your pages.
- 3Avoid JavaScript-driven top navigation entirely when possible.
Code examples
Validate before redirecting top frame
// BAD: top.location.href = userInput; // redirects parent frame to arbitrary URL
// GOOD: validate and restrict
function frameRedirect(url) {
const parsed = new URL(url, top.location.origin);
if (parsed.origin !== top.location.origin) throw new Error("Cross-origin blocked");
top.location.href = parsed.href;
}References
Detected automatically by VulnRadar. The check id is code-redirect-top-location, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is top.location / parent.location assignment?
- 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-top-location, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does top.location / parent.location assignment 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.