# CVE-2025-2539: File Away <= 3.9.9.0.1 - Missing Authorization to Unauthenticated Arbitrary File Read

> Unauthenticated attackers can read arbitrary files on the server due to missing authorization checks in the File Away WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-c39q-wr4f-xpw7

## What is CVE-2025-2539?

CVE-2025-2539 is a high-severity missing authorization vulnerability in thomstark File Away, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2025-2539?

It affects 1 product.


Products: File Away Project File Away.

## How do I fix CVE-2025-2539?

No fix has been published for CVE-2025-2539 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2539 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2539 exists.

Public exploit code:

- File Away <= 3.9.9.0.1 - Missing Authorization to Unauthenticated Arbitrary File Read (github_poc): https://github.com/verylazytech/CVE-2025-2539
- Unauthenticated Arbitrary File Read exploit for WordPress File Away Plugin ≤ 3.9.9.0.1 (github_poc): https://github.com/RootHarpy/CVE-2025-2539
- CVE-2025-2539 - WordPress File Away <= 3.9.9.0.1 - Arbitrary File Read (github_poc): https://github.com/Yucaerin/CVE-2025-2539
- https://github.com/d4rkh0rse/CVE-2025-2539 (github_poc): https://github.com/d4rkh0rse/CVE-2025-2539
- CVE-2025-2539 - File Away WordPress Plugin Arbitrary File Read (github_poc): https://github.com/fazaroot/CVE-2025-2539---File-Away-WordPress-Plugin-Arbitrary-File-Read
- File Away <= 3.9.9.0.1 - Missing Authorization to Unauthenticated Arbitrary File Read (nuclei): http/cves/2025/CVE-2025-2539.yaml

## Other vulnerabilities in thomstark File Away

- [CVE-2025-2512](https://insights.sbomify.com/CVE-2025-2512/): File Away <= 3.9.9.0.1 - Missing Authorization to Unauthenticated File Upload via upload Function (critical 9.8)
- [CVE-2023-0431](https://insights.sbomify.com/CVE-2023-0431/): File Away <= 3.9.9.0.1 - Contributor+ Stored XSS via Shortcode (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2539 and fix it if it is affected.

What it is: CVE-2025-2539 is a high-severity missing authorization vulnerability in thomstark File Away, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2539 exists.

Affected product: thomstark File Away. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2539/ (Markdown: https://insights.sbomify.com/CVE-2025-2539/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2539
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2539
- OSV: https://osv.dev/vulnerability/CVE-2025-2539

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2539/
Summaries are generated and may contain mistakes; the official description above is the record.