File Away <= 3.9.9.0.1 - Missing Authorization to Unauthenticated Arbitrary File Read
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- File Away
- Affected Version
<= 3.9.9.0.1- CVSS
- 7.5High
- Weakness type
- CWE-327 · Use of a Broken or Risky Cryptographic Algorithm
- CVE
CVE-2025-2539
At a glance
CVE-2025-2539 is a high-severity Use of a Broken or Risky Cryptographic Algorithm vulnerability in the File Away WordPress plugin, affecting versions <= 3.9.9.0.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed March 2025, reported by Sélim Lanouar (whattheslime).
Vulnerability Overview
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.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-327: Use of a Broken or Risky Cryptographic Algorithm
The product uses a broken or risky cryptographic algorithm or protocol.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C