This page lists publicly disclosed CVE vulnerabilities affecting 10up safe_svg (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2024-8378 | The Safe SVG WordPress plugin before 2.2.6 has its sanitisation code is only running for paths that call wp_handle_upload, but not for example for code that uses wp_handle_sideload which is often used to upload attachments via raw POST data. | [email protected] | 4.8 | 0.16% | 2024-11-07 | 2025-05-17 |
| CVE-2022-1091 | The sanitisation step of the Safe SVG WordPress plugin before 1.9.10 can be bypassed by spoofing the content-type in the POST request to upload a file. Exploiting this vulnerability, an attacker will be able to perform the kinds of attacks that this plugin should prevent (mainly XSS, but depending on further use of uploaded SVG files potentially other XML attacks). | [email protected] | 6.1 | 0.47% | 2022-04-18 | 2024-11-21 |
| CVE-2019-18855 | A Denial Of Service vulnerability exists in the safe-svg (aka Safe SVG) plugin through 1.9.4 for WordPress, related to potentially unwanted elements or attributes. | [email protected] | 7.5 | 0.63% | 2019-11-11 | 2024-11-21 |
| CVE-2019-18854 | A Denial Of Service vulnerability exists in the safe-svg (aka Safe SVG) plugin through 1.9.4 for WordPress, related to unlimited recursion for a '<use ... xlink:href="#identifier">' substring. | [email protected] | 7.5 | 0.63% | 2019-11-11 | 2024-11-21 |