CVE-2025-64230

Filr <= 1.2.10 - Authenticated (Contributor+) Arbitrary File Deletion

2025-08-17 00:00
Phat RiO

Strategic Overview

Status
Patched in 1.2.11
Affected Version
<= 1.2.10
CVSS
8.1High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2025-64230
View all Filr – Secure document library vulnerabilities

At a glance

CVE-2025-64230 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Filr WordPress plugin, affecting versions <= 1.2.10. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.2.11; sites on affected versions should update now. Disclosed August 2025, reported by Phat RiO.

Vulnerability Overview

The Filr – Secure document library plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in a function in all versions up to, and including, 1.2.10. This makes it possible for authenticated attackers, with Contributor-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).

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 interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Filr <= 1.2.10 takes an account at Contributor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Filr the fix is 1.2.11: builds <= 1.2.10 are affected, anything from 1.2.11 onward is not.

Remediation

Update to version 1.2.11, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Filr 1.2.11 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C