How to fix: target=_blank with javascript: href
Anchor patterns like <a target="_blank" href="javascript:..."> combine reverse tabnabbing risk with javascript: URL execution. Even with noopener, javascript: still runs in the new tab.
Why it matters
Opening a javascript: URL in a new tab executes attacker code in that tab's origin context.
The `code-clickjack-target-blank-js-href` check verifies that the server does not expose the `clickjack-target-blank-js-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
- 1Validate href against an allowlist of http(s) URLs; reject javascript:, data:, vbscript:.
- 2Set rel="noopener noreferrer" on every target="_blank" anchor.
- 3Adopt Trusted Types to gate javascript: URLs.
Code examples
Add rel="noopener noreferrer" to target=_blank links
// BAD: window.opener is accessible from the new tab
window.open(url, "_blank");
// GOOD: noopener prevents opener access
window.open(url, "_blank", "noopener,noreferrer");
// In HTML:
// <a href="..." target="_blank" rel="noopener noreferrer">Link</a>References
Detected automatically by VulnRadar. The check id is code-clickjack-target-blank-js-href, 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 target=_blank with javascript: href?
- 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-clickjack-target-blank-js-href, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does target=_blank with javascript: href map to?
- It maps to CWE-1022. In the OWASP Top 10 it falls under A05: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.