CVE-2020-24948

Autoptimize <= 2.7.6 - Authenticated Arbitrary File Upload

2020-08-24 00:00
Nguyen Van Khanh

Strategic Overview

Status
Patched in 2.7.7
Affected Plugin
Autoptimize
Affected Version
<= 2.7.6
CVSS
7.2High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2020-24948
View all Autoptimize vulnerabilities

At a glance

CVE-2020-24948 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Autoptimize WordPress plugin, affecting versions <= 2.7.6. 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. The issue is fixed in version 2.7.7; sites on affected versions should update now. Disclosed August 2020, reported by Nguyen Van Khanh.

Vulnerability Overview

The ao_ccss_import AJAX call in Autoptimize Wordpress Plugin 2.7.6 does not ensure that the file provided is a legitimate Zip file, allowing high privilege users to upload arbitrary files, such as PHP, leading to remote command execution.

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 Autoptimize <= 2.7.6 takes any authenticated account. 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 Autoptimize the fix is 2.7.7: builds <= 2.7.6 are affected, anything from 2.7.7 onward is not.

Remediation

Update to version 2.7.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Autoptimize: 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: Autoptimize 2.7.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-24948https://www.wordfence.com/threat-intel/vulnerabilities/id/09152aa7-5c10-416a-aa77-a0cde1b6442ehttps://nvd.nist.gov/vuln/detail/CVE-2020-24948

Related records

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