CVE-2025-4799
No exploitation reported by the sources we read.
- Published2025-06-11
- Fixed in1.68.11
- WeaknessCWE-36
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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, 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.
Timeline
dates in UTC- 2025-06-1104:15CVE publishedNVD
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.68 | < 1.68.11 | 1.68.11 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As Wordfence, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- gamerz WP-DownloadManagerother versions: not affectedAffected
- ≤ 1.68.10no fix statedsemver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-08
Fix
- Update Wp-downloadmanager project wp-downloadmanager to 1.68.11
Advisories and patches
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2025-06-11
- CNACVSS 3.17.2known since 2026-10-23
- CNAweakness (CWE)CWE-36known since 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-11-18
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2025-18083same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-xj4j-7mrg-84hqsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Published
- 2025-06-11
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-xj4j-7mrg-84hq
Frequently asked questions
What is CVE-2025-4799?
Is CVE-2025-4799 actively exploited?
What is the CVSS score for CVE-2025-4799?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-xj4j-7mrg-84hq
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- CISA Vulnrichment · CC0-1.0