Cyber Resilience

CVE-2025-4799

Path Traversal in Wp-Downloadmanager Project Wp-Downloadmanager ≤ 1.68.11

Published
11 June 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0081 54th percentile
Risk Priority 60 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-4799 is a high-severity Absolute Path Traversal (CWE-36) vulnerability in Wp-Downloadmanager Project Wp-Downloadmanager. Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The WP-DownloadManager plugin for WordPress is vulnerable to arbitrary file deletion in all versions through 1.68.10. The flaw stems from insufficient path restrictions when handling file deletion requests, allowing an attacker to specify files outside an intended directory. This is tracked as CWE-36 and carries a CVSS 3.1 score of 7.2.

Authenticated users with Administrator privileges can exploit the issue to remove arbitrary files on the underlying server. Successful deletion of critical files such as wp-config.php can result in remote code execution. The vulnerability can also be chained with CVE-2025-4798 to target any file inside the WordPress root directory.

Public references include the plugin's source files on WordPress Trac and changeset 3294467, which implements a fix. The Wordfence advisory associated with the CVE further documents the affected code paths and confirms that an updated version addressing the path-handling weakness is available.

EPSS for the CVE remains flat at 0.0728 with no material increase observed after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The WP-DownloadManager plugin for WordPress is vulnerable to arbitrary file deletion due to lack of restriction on the directory a file can be deleted from in all versions up to, and including, 1.68.10. This makes it possible for authenticated attackers,…

more

with Administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). This vulnerability can be paired with CVE-2025-4798 to delete any file within the WordPress root directory.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-4798Same product: Wp-Downloadmanager Project Wp-Downloadmanager
CVE-2023-28989Same product class: WordPress / CMS plugin
CVE-2025-1323Same product class: WordPress / CMS plugin
CVE-2023-47679Same product class: WordPress / CMS plugin
CVE-2023-47519Same product class: WordPress / CMS plugin
CVE-2023-35912Same product class: WordPress / CMS plugin
CVE-2024-0515Same product class: WordPress / CMS plugin
CVE-2023-47178Same product class: WordPress / CMS plugin
CVE-2023-25976Same product class: WordPress / CMS plugin
CVE-2023-0086Same product class: WordPress / CMS plugin

Affected Assets

wp-downloadmanager project
wp-downloadmanager
≤ 1.68.11

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly stops construction of absolute paths from untrusted data before they reach file operations.

Enforced access authorizations can limit which resources are reachable even if a traversal succeeds.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent absolute path traversal.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect absolute path traversal via static analysis and fuzzing.

prevents

Secure development lifecycle includes input validation and path-handling requirements that reduce absolute path traversal risk.

prevents

Application security requirements typically mandate controls against path traversal in file-access functions.

prevents

Secure architecture principles call for canonicalization and sandboxing that limit absolute path traversal.

prevents

Secure coding standards directly require neutralization of absolute path sequences in pathname construction.

mitigates

Information access restriction limits which files can be reached but does not address the path-construction flaw itself.

References