CVE-2020-24146

CM Download Manager < 2.8.0 - Directory Traversal to Arbitrary File Deletion and Denial of Service

Strategic Overview

Status
Patched in 2.8.0
Affected Version
< 2.8.0
CVSS
8.1High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2020-24146
View all CM Download Manager – Organize, Protect & Share Files in WordPress vulnerabilities

At a glance

CVE-2020-24146 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the CM Download Manager WordPress plugin, affecting versions < 2.8.0. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). The issue is fixed in version 2.8.0; sites on affected versions should update now. Disclosed April 2021, reported by Suzhou Aurora Infinity Information Technology Co.

Vulnerability Overview

Directory traversal in the CM Download Manager (aka cm-download-manager) plugin 2.7.0 for WordPress allows authorized users to delete arbitrary files and possibly cause a denial of service via the fileName parameter in a deletescreenshot action.

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 integrity, availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in CM Download Manager < 2.8.0 takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For CM Download Manager the fix is 2.8.0: builds < 2.8.0 are affected, anything from 2.8.0 onward is not.

Remediation

Update to version 2.8.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to CM Download Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CM Download Manager 2.8.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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