Checkout Field Editor for WooCommerce (Pro) <= 3.7.7 - Authenticated (Subscriber+) Path Traversal to Arbitrary File Read via 'thwcfe_legacy_file' Parameter
Strategic Overview
- Status
- Patched in 3.7.8
- Affected Plugin
- Checkout Field Editor for WooCommerce (Pro)
- Affected Version
<= 3.7.7- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-14955
At a glance
CVE-2026-14955 is a medium-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.7.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.7.8; sites on affected versions should update now. Disclosed July 2026, reported by 0xd4rk5id3.
Vulnerability Overview
The Checkout Field Editor for WooCommerce (Pro) plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 3.7.7 via the 'thwcfe_legacy_file' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to read the contents 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. A successful exploit has high impact on confidentiality.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Checkout Field Editor for WooCommerce (Pro) <= 3.7.7 carries this weakness at thwcfe_legacy_file, 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 Checkout Field Editor for WooCommerce (Pro) the fix is 3.7.8: builds <= 3.7.7 are affected, anything from 3.7.8 onward is not.
Remediation
Update to version 3.7.8, 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: Checkout Field Editor for WooCommerce (Pro) 3.7.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C