Checkout Field Editor for WooCommerce (Pro) <= 3.6.2 - Unauthenticated Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 3.6.3
- Affected Plugin
- Checkout Field Editor for WooCommerce (Pro)
- Affected Version
<= 3.6.2- CVSS
- 9.8Critical
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2024-35658
At a glance
CVE-2024-35658 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Checkout Field Editor for WooCommerce (Pro) WordPress plugin, affecting versions <= 3.6.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.6.3; sites on affected versions should update now. Disclosed June 2024, reported by Dave Jong.
Vulnerability Overview
The Checkout Field Editor for WooCommerce (Pro) plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 3.6.2. This is due to the plugin not properly validating a file or it's path prior to deleting it. This makes it possible for unauthenticated attackers to delete arbitrary files which can be leveraged to achieve remote code execution.
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 confidentiality, integrity, availability — full site compromise territory.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Checkout Field Editor for WooCommerce (Pro) <= 3.6.2 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 Checkout Field Editor for WooCommerce (Pro) the fix is 3.6.3: builds <= 3.6.2 are affected, anything from 3.6.3 onward is not.
Remediation
Update to version 3.6.3, 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: Checkout Field Editor for WooCommerce (Pro) 3.6.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C