Radar sectionsDatabase
Check my site
WordPress plugin

Safe SVG <= 1.9.9 — Content-Type Bypass

CVE-2022-1091Published · Updated

Action summary

Affected: <1.9.10Update to 1.9.10 or newer

All remediation steps
Severity
High7.7
CVSS
7.7
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:C Scope
Changed
C:N Confidentiality
None
I:H Integrity
High
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Safe SVG safe-svg

  1. Affected< 1.9.10
  2. Patched in1.9.10

Update to 1.9.10 or newer.

You are affected if you run < 1.9.10. Version 1.9.10 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Safe SVG.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 1.9.10, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Safe SVG to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to David Hamann.

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).

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Safe SVG

All 8
More vulnerabilities in Safe SVG
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤2.5.0Update to 2.5.1
CVE-2026-94077
Medium4.3Authenticated (Contributor+) Insecure Direct Object Reference
≤2.5.0Update to 2.5.1
CVE-2026-94672
Medium5.4Authenticated (Author+) Stored Cross-Site Scripting via SVG
≤2.2.5Update to 2.2.6
CVE-2024-8378
High7.2Cross-Site Scripting Bypass
≤2.0.3Update to 2.1.0
CVE-2023-28426
Medium5.4Cross-Site Scripting
≤1.9.5Update to 1.9.6
—

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 7.7

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?