WP User Frontend Pro <= 4.1.3 - Authenticated (Subscriber+) Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 4.1.4
- Affected Plugin
- WP User Frontend Pro
- Affected Version
<= 4.1.3- CVSS
- 8.1High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-3055
At a glance
CVE-2025-3055 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP User Frontend Pro WordPress plugin, affecting versions <= 4.1.3. 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 Subscriber level or above. The issue is fixed in version 4.1.4; sites on affected versions should update now. Disclosed June 2025, reported by Foxyyy.
Vulnerability Overview
The WP User Frontend Pro plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_avatar_ajax() function in all versions up to, and including, 4.1.3. This makes it possible for authenticated attackers, with Subscriber-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')
WP User Frontend Pro <= 4.1.3 carries this weakness at delete_avatar_ajax(), and reaching it takes an account at Subscriber 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 WP User Frontend Pro the fix is 4.1.4: builds <= 4.1.3 are affected, anything from 4.1.4 onward is not.
Remediation
Update to version 4.1.4, 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. None of that substitutes for the fix: WP User Frontend Pro 4.1.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP User Frontend Pro
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C