ProSolution WP Client <= 2.0.8 - Unauthenticated Arbitrary File Deletion via 'newfilename' and 'filename' Parameters
Strategic Overview
- Status
- Patched in 2.0.9
- Affected Plugin
- ProSolution WP Client
- Affected Version
<= 2.0.8- CVSS
- 9.1Critical
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-14524
At a glance
CVE-2026-14524 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the ProSolution WP Client WordPress plugin, affecting versions <= 2.0.8. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.9; sites on affected versions should update now. Disclosed August 2026, reported by CHOIGYEONGMIN.
Vulnerability Overview
The ProSolution WP Client plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the proSol_fileDeleteProcess function in all versions up to, and including, 2.0.8. This makes it possible for unauthenticated attackers 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). An attacker must first call the proSol_fileUploadModalProcess handler to poison their own session with a path-traversal key, then call proSol_fileDeleteProcess with that key as the filename parameter; both steps require only the publicly exposed frontend nonce.
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 privileges on the target site, 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 ProSolution WP Client <= 2.0.8 takes no account at all. 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 ProSolution WP Client the fix is 2.0.9: builds <= 2.0.8 are affected, anything from 2.0.9 onward is not.
Remediation
Update to version 2.0.9, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ProSolution WP Client 2.0.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in ProSolution WP Client
- 9.8CVE-2026-16098: ProSolution WP Client <= 2.0.10 Arbitrary File Upload
CVE-2026-16098 - 9.8CVE-2026-6555: ProSolution WP Client <= 2.0.0 Arbitrary File Upload
CVE-2026-6555 - 9.8CVE-2026-2942: ProSolution WP Client <= 1.9.9 Arbitrary File Upload
CVE-2026-2942 - 7.5CVE-2026-19053: ProSolution WP Client <= 2.0.5 SQL Injection
CVE-2026-19053 - 7.5CVE-2026-19049: ProSolution WP Client <= 2.0.8 SQL Injection
CVE-2026-19049 - 4.3CVE-2026-19052: ProSolution WP Client <= 2.0.8 Missing Authorization
CVE-2026-19052
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C