How to fix: Missing sandbox attribute on iframe
An iframe element is present without a sandbox attribute, giving the embedded content full access to the same privileges as the parent page.
Why it matters
Without sandbox, an iframe has the same-origin privileges as the parent page, third-party content can access parent DOM, cookies, and run scripts with no restrictions.
The sandbox attribute restricts iframe capabilities by default and allows adding back only the required permissions.
How to fix it
- 1Add sandbox="" to the iframe element
- 2Add specific permissions as needed: allow-scripts, allow-forms, allow-same-origin
- 3Never combine allow-scripts with allow-same-origin for cross-origin untrusted content
Code examples
Add sandbox attribute
<!-- Unsafe: no sandbox -->
<iframe src="https://third-party.com"></iframe>
<!-- Safe: sandboxed -->
<iframe src="https://third-party.com" sandbox="allow-scripts allow-forms"></iframe>References
Detected automatically by VulnRadar. The check id is iframe-sandbox-missing, 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 Missing sandbox attribute on iframe?
- 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 iframe-sandbox-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing sandbox attribute on iframe 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.