CVE-2024-5080

Wp EMember <= 10.6.5 - Authenticated (Admin+) Arbitrary File Upload

2024-06-22 00:00
Bob Matyas

Strategic Overview

Status
Patched in 10.6.6
Affected Plugin
Wp EMember
Affected Version
<= 10.6.5
CVSS
9.1Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2024-5080
View all Wp EMember vulnerabilities

At a glance

CVE-2024-5080 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Wp EMember WordPress plugin, affecting versions <= 10.6.5. It carries a CVSS score of 9.1 (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 10.6.6; sites on affected versions should update now. Disclosed June 2024, reported by Bob Matyas.

Vulnerability Overview

The Wp EMember plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 10.6.5. This makes it possible for authenticated attackers, with administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Wp EMember <= 10.6.5 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 Wp EMember the fix is 10.6.6: builds <= 10.6.5 are affected, anything from 10.6.6 onward is not.

Remediation

Update to version 10.6.6, 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: Wp EMember 10.6.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-5080https://www.wordfence.com/threat-intel/vulnerabilities/id/3a4179ef-c98b-42c9-b7e5-a42bc46eaad1https://nvd.nist.gov/vuln/detail/CVE-2024-5080

Related records

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