Skip to main content

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

  1. 1Ensure srcdoc content is properly sanitized.

Code examples

Sanitize srcdoc content and add sandbox

HTML
<!-- 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.

See every content check

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.

Propose a checkHow a check is built

Scan your own site for iframe with srcdoc attribute

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Iframe with srcdoc Attribute | VulnRadar