Orders Tracking for WooCommerce <= 1.2.5 - Authenticated (Administrator+) Directory Traversal via 'file_url'
Strategic Overview
- Status
- Patched in 1.2.6
- Affected Plugin
- Trakoo – Orders Tracking for WooCommerce
- Affected Version
<= 1.2.5- CVSS
- 2.7Low
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2023-4216
At a glance
CVE-2023-4216 is a low-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Trakoo WordPress plugin, affecting versions <= 1.2.5. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.2.6; sites on affected versions should update now. Disclosed August 2023, reported by Utkarsh Agrawal.
Vulnerability Overview
The Orders Tracking for WooCommerce plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 1.2.5 via the 'file_url' parameter when importing CSV files. This allows authenticated attackers, with administrator-level (manage_woocommerce) privileges and above, to read the contents of the first line of arbitrary files on the server, which can contain sensitive information.
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-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Trakoo <= 1.2.5 carries this weakness at file_url, and reaching it takes an account at Administrator 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 Trakoo the fix is 1.2.6: builds <= 1.2.5 are affected, anything from 1.2.6 onward is not.
Remediation
Update to version 1.2.6, or a newer patched version
How does WordSec protect against this?
An attacker needs Administrator 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: Trakoo 1.2.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Trakoo – Orders Tracking for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C