CVE-2025-2539
A public proof of concept exists; no exploitation attested.
- Published2025-03-20
- WeaknessCWE-327
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 File Away plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the ajax() function in all versions up to, and including, 3.9.9.0.1. This makes it possible for unauthenticated attackers, leveraging the use of a reversible weak algorithm, to read the contents of arbitrary files on the server, which can contain sensitive information.
Timeline
dates in UTC- 2025-03-2012:15CVE publishedNVD
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.9 | ≤ 3.9.9.0.1 | no fix published | 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.
- thomstark File Awayother versions: not affectedAffected
- ≤ 3.9.9.0.1no fix statedsemver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-03-20
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- available ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHub5 repositories, unverifiedknown since 2026-11-01verylazytech/CVE-2025-2539RootHarpy/CVE-2025-2539Yucaerin/CVE-2025-2539d4rkh0rse/CVE-2025-2539fazaroot/CVE-2025-2539---File-Away-WordPress-Plugin-Arbitrary-File-Read
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2025-03-20
- CNACVSS 3.17.5known since 2026-10-23
- CNAweakness (CWE)CWE-327known since 2026-10-23
- FIRST EPSSEPSS score1.7 %2026-11-19
- PoC-in-GitHubproof of concept5known since 2026-11-01
- ProjectDiscoverydetectionread 2026-11-20
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2025-6807same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-c39q-wr4f-xpw7same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2025-03-20
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-c39q-wr4f-xpw7
Frequently asked questions
What is CVE-2025-2539?
Is CVE-2025-2539 actively exploited?
What is the CVSS score for CVE-2025-2539?
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-c39q-wr4f-xpw7
- Nuclei templates · MIT
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0