CVE-2026-2419

WP-DownloadManager <= 1.69 - Authenticated (Administrator+) Path Traversal to Arbitrary File Read via 'download_path' Parameter

2026-02-17 19:12
n4ur15

Strategic Overview

Status
Patched in 1.69.1
Affected Plugin
WP-DownloadManager
Affected Version
<= 1.69
CVSS
2.7Low
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-2419
View all WP-DownloadManager vulnerabilities

At a glance

CVE-2026-2419 is a low-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP-DownloadManager WordPress plugin, affecting versions <= 1.69. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.69.1; sites on affected versions should update now. Disclosed February 2026, reported by n4ur15.

Vulnerability Overview

The WP-DownloadManager plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.69 via the 'download_path' configuration parameter. This is due to insufficient validation of the download path setting, which allows directory traversal sequences to bypass the WP_CONTENT_DIR prefix check. This makes it possible for authenticated attackers, with Administrator-level access and above, to configure the plugin to list and access arbitrary files on the server by exploiting the file browser functionality. CVE-2026-18933 is likely a duplicate.

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.

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

WP-DownloadManager <= 1.69 carries this weakness at download_path, and reaching it takes an account at Administrator level or above. 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 WP-DownloadManager the fix is 1.69.1: builds <= 1.69 are affected, anything from 1.69.1 onward is not.

Remediation

Update to version 1.69.1, 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. None of that substitutes for the fix: WP-DownloadManager 1.69.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2419https://www.wordfence.com/threat-intel/vulnerabilities/id/0bb96da1-9c17-4264-ac29-b5ff8dec745dhttps://nvd.nist.gov/vuln/detail/CVE-2026-2419

Related records

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