How to fix: Window.opener Access Detected
JavaScript accesses window.opener properties, exploitable for reverse tabnabbing.
Why it matters
Can redirect the parent tab to a phishing page without the user noticing.
When a page is opened via window.open() or target='_blank', it may have a reference to the opening window.
How to fix it
- 1Add rel='noopener noreferrer' to external links.
- 2Set window.opener = null at the top of pages.
- 3Use Cross-Origin-Opener-Policy: same-origin.
Code examples
Safe link
<a href="https://external.com" target="_blank" rel="noopener noreferrer">External</a>References
Detected automatically by VulnRadar. The check id is window-opener-abuse, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Window.opener Access Detected?
- VulnRadar rates this medium severity in the content 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 window-opener-abuse, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Window.opener Access Detected 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.