Medium severity · published Apr 18, 2022
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
6.1
CVSS
1.2%
EPSS
No
On KEV
Description
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).
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)1.2% · higher than 68% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SS
Safe Svg · 10up
before 1.9.10 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-1091
CVE.org
https://www.cve.org/CVERecord?id=CVE-2022-1091
Patch
https://github.com/10up/safe-svg/pull/28
Exploit
https://wpscan.com/vulnerability/4d12533e-bdb7-411f-bcdf-4c5046db13f3
More from Safe Svg
7.5
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
7.5
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
6.5
CVE-2026-94077
WordPress Safe SVG plugin <= 2.5.0 - Cross Site Scripting (XSS) vulnerability
4.8
CVE-2024-8378
Safe SVG < 2.2.6 - Author+ SVG Sanitisation Bypass
4.3
CVE-2026-94672
WordPress Safe SVG plugin <= 2.5.0 - Insecure Direct Object References (IDOR) vulnerability
