Path traversal in ThemeHigh Checkout Field Editor for WooCommerce
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-22 and the CVSS impact.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-14955
- 2026-10-03 Alias added: GHSA-xghp-9m6j-2mx2
References
More ThemeHigh vulnerabilities
- TI-2022-03221 Checkout Field Editor for WooCommerce < 1.8.0 - Admin+ PHP Object Injection CVSS 3.1HIGH 7.2
- TI-2024-00649 Stripe Payment Plugin for WooCommerce <= 3.7.9 - Unauthenticated SQL Injection CVSS 3.1CRITICAL 9.8
- TI-2022-00692 Multiple Shipping Address Woocommerce < 2.0 - Unauthenticated SQLi CVSS 3.1CRITICAL 9.8
- TI-2023-02962 Stripe Payment Plugin for WooCommerce <= 3.7.7 - Authentication Bypass CVSS 3.1CRITICAL 9.8
- TI-2024-23527 Path traversal in ThemeHigh Checkout Field Editor for WooCommerce CVSS 3.1CRITICAL 9.1
- TI-2026-74618 Remote code execution in Email Customizer for WooCommerce (Pro) CVSS 3.1HIGH 8.8
Sources
- CVE-2026-14955 · CVE Program
- CVE-2026-14955 · NVD
- FIRST EPSS
- GHSA-xghp-9m6j-2mx2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences