WP-DownloadManager <= 1.69 - Authenticated (Administrator+) Path Traversal to Arbitrary File Read via 'download_path' Parameter
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
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.
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
Related records
Same weakness class
Other vulnerabilities in WP-DownloadManager
- 7.2CVE-2025-10747: WP-DownloadManager <= 1.68.11 Arbitrary File Upload
CVE-2025-10747 - 7.2CVE-2025-4799: WP-DownloadManager <= 1.68.10 Arbitrary File Deletion
CVE-2025-4799 - 6.1CVE-2024-47341: WP-DownloadManager <= 1.68.8 Reflected XSS
CVE-2024-47341 - 5.3CVE-2020-24141: WP-DownloadManager <= 1.68.4 SSRF
CVE-2020-24141 - 4.9CVE-2025-4798: WP-DownloadManager <= 1.68.10 Arbitrary File Read
CVE-2025-4798 - 4.8CVE-2022-25605: WP-DownloadManager plugin <= 1.68.6 Stored XSS
CVE-2022-25605 - 4.8CVE-2022-25606: WP-DownloadManager <= 1.68.6 Stored XSS
CVE-2022-25606 - 4.8CVE-2021-44760: WP-DownloadManager plugin <= 1.68.6 Reflected XSS
CVE-2021-44760
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C