CVE-2025-13382

Frontend File Manager Plugin <= 23.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary File Renaming

2025-11-24 19:15
t.t.brothers

Strategic Overview

Status
Patched in 23.5
Affected Version
<= 23.4
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-13382
View all Frontend File Manager Plugin vulnerabilities

At a glance

CVE-2025-13382 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Frontend File Manager Plugin WordPress plugin, affecting versions <= 23.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 23.5; sites on affected versions should update now. Disclosed November 2025, reported by t.t.brothers.

Vulnerability Overview

The Frontend File Manager Plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 23.4. This is due to the plugin not validating file ownership before processing file rename requests in the '/wpfm/v1/file-rename' REST API endpoint. This makes it possible for authenticated attackers, with Subscriber-level access and above, to rename files uploaded by other users via the 'fileid' parameter.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Frontend File Manager Plugin <= 23.4 carries this weakness at fileid, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Frontend File Manager Plugin the fix is 23.5: builds <= 23.4 are affected, anything from 23.5 onward is not.

Remediation

Update to version 23.5, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Frontend File Manager Plugin 23.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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