LowContent
How to fix: Iframe with srcdoc Attribute
Iframe using srcdoc for inline HTML.
Why it matters
Inline HTML in iframes can be complex to secure.
srcdoc allows HTML directly in iframe.
How to fix it
- 1Ensure srcdoc content is properly sanitized.
Code examples
Sanitize srcdoc content and add sandbox
<!-- BAD: srcdoc from user input without sandbox -->
<!-- <iframe srcdoc="{{ userHtml }}"></iframe> -->
<!-- GOOD: sanitize srcdoc content and restrict with sandbox -->
<iframe
srcdoc="<!-- sanitized HTML only -->
<p>Safe content</p>"
sandbox=""
title="Safe frame"
></iframe>References
Detected automatically by VulnRadar. The check id is srcdoc-iframe, 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 with srcdoc Attribute?
- 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 srcdoc-iframe, which stays the same between runs so you can filter, diff, or gate CI on it.
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.