How to fix: Iframe Sandbox Allows Scripts
Sandboxed iframe with allow-scripts.
Why it matters
Sandboxed content can still execute JavaScript.
allow-scripts re-enables JavaScript in sandbox.
How to fix it
- 1Only add allow-scripts if absolutely necessary.
Code examples
Minimize sandbox permissions on iframes
<!-- Start with most restrictive and add only what the iframe needs -->
<iframe
src="https://widget.example.com"
sandbox="allow-scripts"
title="Widget"
></iframe>
<!-- Avoid combining allow-scripts + allow-same-origin: this effectively removes sandboxing -->
<!-- Use allow-same-origin only for same-origin trusted content -->References
Detected automatically by VulnRadar. The check id is sandbox-allow-scripts, 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 Iframe Sandbox Allows Scripts?
- VulnRadar rates this low 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 sandbox-allow-scripts, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Iframe Sandbox Allows Scripts 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.