dbcve.org
File AwayWordPress extension · File Away Project

CVE-2025-2539

HIGH · 7.5 CVSS v3.1 Published 2025-03-20
Fix available
A fix is available. Upgrade to after 3.9.9.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The File Away WordPress plugin lacks a capability check on its ajax() function, allowing unauthenticated attackers to exploit a reversible weak algorithm to read arbitrary files on the server, potentially exposing sensitive configuration or data files.

MitigationUpdate the File Away plugin to a version beyond 3.9.9.0.1 once a patched release is available, or remove the plugin entirely if no fix is forthcoming.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
File AwayWordPress extension
Affected:<= 3.9.9.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if File Away plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'File Away' or 'Project File Away'. Note the version number displayed next to the plugin name.
    Affected if The plugin is installed and the version is 3.9.9.0.1 or lower.
  2. Verify the plugin version
    Check the plugin header file (usually at wp-content/plugins/file-away/fileaway.php or similar path) for the 'Version' defined in the plugin metadata. Compare this against the affected range <= 3.9.9.0.1.
    Affected if The installed version number is 3.9.9.0.1 or any version lower than that.
  3. Confirm ajax functionality is accessible
    Check if the WordPress site has the ajax functionality exposed. This can be verified by examining if the file-away-ajax or similar endpoint responds. Look for wp-admin/admin-ajax.php being accessible without authentication, and check if the File Away plugin registers ajax actions (search for 'wp_ajax_fileaway' or 'wp_ajax_nopriv_fileaway' in plugin code).
    Affected if The plugin's ajax function is registered and accessible to unauthenticated users (nopriv).
  4. Check for weak algorithm configuration
    Examine the plugin settings in WordPress admin under the File Away configuration panel. Look for any options related to encryption, obfuscation, or file access that use a reversible algorithm. Check the plugin source code for functions using base64_encode, str_rot13, or similar weak reversible methods.
    Affected if A reversible weak algorithm (like base64 or simple rotation) is enabled in the plugin settings or used in the ajax file-reading logic.
  5. Verify file access exposure
    Review server logs or use a test request to see if the ajax endpoint can be triggered without authentication to read arbitrary files. Attempt a controlled test request to the ajax endpoint with a known file path to confirm if arbitrary file reading is possible.
    Affected if The ajax function allows reading files outside the intended directory or can be exploited without authentication.

The environment is affected if the File Away plugin version is 3.9.9.0.1 or lower AND the ajax functionality is accessible to unauthenticated users AND a reversible weak algorithm is in use for file operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.9.9.0.1
Interim mitigation

Update the File Away plugin to a version beyond 3.9.9.0.1 once a patched release is available, or remove the plugin entirely if no fix is forthcoming.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (check for version > 3.9.9.0.1)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'File Away' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. If no update is shown, manually download the latest version from wordpress.org/plugins/file-away and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly and test that the ajax functionality works as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in File Away Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2539 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data