CVE-2025-13320

WP User Manager <= 2.9.12 - Authenticated (Subscriber+) Arbitrary File Deletion via 'current_user_avatar' Parameter

2025-12-11 15:08
YC_Infosec

Strategic Overview

Status
Patched in 2.9.13
Affected Version
<= 2.9.12
CVSS
6.8Medium
Weakness type
CWE-73 · External Control of File Name or Path
CVE
CVE-2025-13320
View all WP User Manager – User Profile Builder & Membership vulnerabilities

At a glance

CVE-2025-13320 is a medium-severity External Control of File Name or Path vulnerability in the WP User Manager WordPress plugin, affecting versions <= 2.9.12. It carries a CVSS score of 6.8 (reachable over the network; high integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.9.13; sites on affected versions should update now. Disclosed December 2025, reported by YC_Infosec.

Vulnerability Overview

The WP User Manager plugin for WordPress is vulnerable to Arbitrary File Deletion in all versions up to, and including, 2.9.12. This is due to insufficient validation of user-supplied file paths in the profile update functionality combined with improper handling of array inputs by PHP's filter_input() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server via the 'current_user_avatar' parameter in a two-stage attack which can make remote code execution possible. This only affects sites with the custom avatar setting enabled.

Technical Analysis

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

CWE-73: External Control of File Name or Path

The product allows user input to control or influence paths or file names that are used in filesystem operations.

Remediation

Update to version 2.9.13, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP User Manager 2.9.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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