CVE-2022-40217

WPide <= 2.6 - Authenticated (Administrator+) Arbitrary File Upload

2022-08-09 00:00
R3N0

Strategic Overview

Status
Patched in 3.0
Affected Plugin
WPIDE – File Manager & Code Editor
Affected Version
<= 2.6
CVSS
7.2High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2022-40217
View all WPIDE – File Manager & Code Editor vulnerabilities

At a glance

CVE-2022-40217 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WPIDE WordPress plugin, affecting versions <= 2.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 at Administrator level or above. The issue is fixed in version 3.0; sites on affected versions should update now. Disclosed August 2022, reported by R3N0.

Vulnerability Overview

The WPide plugin for WordPress is vulnerable to arbitrary file uploads in versions up to, and including, 2.6. This makes it possible for authenticated attackers, with administrator-level permissions and above, to upload arbitrary files on the affected sites 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 WPIDE <= 2.6 takes an account at Administrator 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 WPIDE the fix is 3.0: builds <= 2.6 are affected, anything from 3.0 onward is not.

Remediation

Update to version 3.0, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator 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: WPIDE 3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-40217https://www.wordfence.com/threat-intel/vulnerabilities/id/c77db815-e401-4410-b6ec-e6668dd988abhttps://nvd.nist.gov/vuln/detail/CVE-2022-40217

Related records

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