The Iframe Project maintains a narrowly scoped web-component library whose vulnerability profile centers on its core iframe product and recurs around cross-site scripting weaknesses arising from input neutralization during page generation. Treat this as a compact vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Iframe Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-4919MEDIUM The iframe plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `iframe` shortcode in versions up to, and including, 4.6 due to insufficient input sanitization | Oct 20, 2023 | 5.4 | 18 | NO | NO |
CVE-2023-52125MEDIUM Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in webvitaly iframe allows Stored XSS.This issue affects iframe: from n/a through | Jan 5, 2024 | 5.4 | 17 | NO | NO |
CVE-2023-24394MEDIUM Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Gopi Ramasamy iframe popup plugin <= 3.3 versions. | Aug 25, 2023 | 4.8 | 17 | NO | NO |
CVE-2020-12696MEDIUM The iframe plugin before 4.5 for WordPress does not sanitize a URL. | May 7, 2020 | 6.1 | 17 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Iframe Project.
Media articles that mention a CVE ID that affects a product developed by Iframe Project — matched by CVE ID, not by vendor name.