WP-DownloadManager <= 1.68.10 - Authenticated (Administrator+) Arbitrary File Read
Strategic Overview
- Status
- Patched in 1.68.11
- Affected Plugin
- WP-DownloadManager
- Affected Version
<= 1.68.10- CVSS
- 4.9Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-4798
At a glance
CVE-2025-4798 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP-DownloadManager WordPress plugin, affecting versions <= 1.68.10. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.68.11; sites on affected versions should update now. Disclosed June 2025, reported by Jamshed Yergashvoyev (CVE Guy).
Vulnerability Overview
The WP-DownloadManager plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 1.68.10. This is due to a lack of restriction on the directory an administrator can select for storing downloads. This makes it possible for authenticated attackers, with Administrator-level access and above, to download and read any file on the server, including system and configuration files.
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.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WP-DownloadManager <= 1.68.10 takes an account at Administrator level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP-DownloadManager the fix is 1.68.11: builds <= 1.68.10 are affected, anything from 1.68.11 onward is not.
Remediation
Update to version 1.68.11, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: WP-DownloadManager 1.68.11 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
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.5CVE-2026-2426: WP-DownloadManager Path Traversal
CVE-2026-2426 - 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.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