CVE-2022-1939

Allow SVG Files <= 1.0 - Authenticated (Admin+) Arbitrary File Upload

2020-05-30 00:00
Luan Pedersini

Strategic Overview

Status
Patched in 1.1
Affected Plugin
Allow svg files
Affected Version
< 1.1
CVSS
7.2High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2022-1939
View all Allow svg files vulnerabilities

At a glance

CVE-2022-1939 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Allow svg files WordPress plugin, affecting versions < 1.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.1; sites on affected versions should update now. Disclosed May 2020, reported by Luan Pedersini.

Vulnerability Overview

The Allow svg files WordPress plugin before 1.1 does not properly validate uploaded files, which could allow high privilege users such as admin to upload PHP files even when they are not allowed to

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in Allow svg files < 1.1 takes an account at Admin level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Allow svg files the fix is 1.1: builds < 1.1 are affected, anything from 1.1 onward is not.

Remediation

Update to version 1.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Allow svg files 1.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C