How to fix: Sandboxed iframe allows both scripts and same-origin
Combining sandbox='allow-scripts allow-same-origin' removes most of the sandbox protection and lets the iframe access the parent origin.
Why it matters
Drop allow-same-origin (or allow-scripts) - together they fully re-enable same-origin script execution
Combining sandbox='allow-scripts allow-same-origin' removes most of the sandbox protection and lets the iframe access the parent origin.
How to fix it
- 1Drop allow-same-origin (or allow-scripts) - together they fully re-enable same-origin script execution
Code examples
Avoid combining allow-scripts and allow-same-origin in sandbox
<!-- DANGEROUS: combining these two effectively removes sandbox protection -->
<!-- The iframe can remove its own sandbox via script -->
<!-- BAD: sandbox="allow-scripts allow-same-origin" for cross-origin content -->
<!-- GOOD: use allow-scripts only for cross-origin untrusted content -->
<iframe src="https://untrusted.example.com" sandbox="allow-scripts" title="Widget"></iframe>
<!-- Only combine allow-scripts + allow-same-origin for your own trusted, same-origin content -->References
Detected automatically by VulnRadar. The check id is iframe-allow-scripts-allow-same-origin, 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 Sandboxed iframe allows both scripts and same-origin?
- VulnRadar rates this high 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 iframe-allow-scripts-allow-same-origin, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Sandboxed iframe allows both scripts and same-origin map to?
- It maps to CWE-1021. 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.