How to fix: Insecure Iframe Sources on HTTPS Page
Iframes loading content over HTTP on an HTTPS page.
Why it matters
HTTP iframes on HTTPS pages create mixed content, allowing MITM attackers to modify iframe content.
Browsers display your page as secure but an HTTP iframe can be intercepted and modified by network attackers.
How to fix it
- 1Change all iframe src attributes to use HTTPS.
- 2Use CSP: frame-src https:.
- 3Consider using the sandbox attribute.
Code examples
CSP
Content-Security-Policy: frame-src https: 'self';References
Detected automatically by VulnRadar. The check id is insecure-iframes, 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 Insecure Iframe Sources on HTTPS Page?
- 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 insecure-iframes, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Insecure Iframe Sources on HTTPS Page map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02: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.