CVE-2025-0818

Multiple elFinder Plugins <= (Various Versions) - Directory Traversal to Arbitrary File Deletion

2025-08-12 00:00
tiborisaak

Strategic Overview

Status
Patched in 1.9
Affected Version
<= 1.8.9
CVSS
6.5Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2025-0818
View all File Manager Pro – Filester vulnerabilities

At a glance

CVE-2025-0818 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the File Manager Pro WordPress plugin, affecting versions <= 1.8.9. It carries a CVSS score of 6.5 (reachable over the network; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.9; sites on affected versions should update now. Disclosed August 2025, reported by tiborisaak.

Vulnerability Overview

Several WordPress plugins using elFinder versions 2.1.64 and prior are vulnerable to Directory Traversal in various versions. This makes it possible for unauthenticated attackers to delete arbitrary files. Successful exploitation of this vulnerability requires a site owner to explicitly make an instance of the file manager available to users.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.

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

Reaching this weakness in File Manager Pro <= 1.8.9 takes a caller who can reach the endpoint. 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 File Manager Pro the fix is 1.9: builds <= 1.8.9 are affected, anything from 1.9 onward is not.

Remediation

Update to version 1.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to File Manager Pro: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: File Manager Pro 1.9 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