CVE-2021-24160

Responsive Menu 4.0 - 4.0.3 - Authenticated Arbitrary File Upload

2021-02-10 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 4.0.4
Affected Version
4.0 – < 4.0.4
CVSS
8.8High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2021-24160
View all Responsive Menu – Create Mobile-Friendly Menu vulnerabilities

At a glance

CVE-2021-24160 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Responsive Menu WordPress plugin, affecting versions 4.0 – < 4.0.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 4.0.4; sites on affected versions should update now. Disclosed February 2021, reported by Chloe Chamberland.

Vulnerability Overview

In the Reponsive Menu (free and Pro) WordPress plugins before 4.0.4, subscribers could upload zip archives containing malicious PHP files that would get extracted to the /rmp-menu/ directory. These files could then be accessed via the front end of the site to trigger remote code execution and ultimately allow an attacker to execute commands to further infect a WordPress site.

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 Responsive Menu 4.0 – < 4.0.4 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 Responsive Menu the fix is 4.0.4: builds 4.0 – < 4.0.4 are affected, anything from 4.0.4 onward is not.

Remediation

Update to version 4.0.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Responsive Menu: 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: Responsive Menu 4.0.4 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