Tax Exempt for WooCommerce <= 1.9.3 - Authenticated (Customer+) Path Traversal
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Tax Exempt for WooCommerce
- Affected Version
<= 1.9.3- CVSS
- 4.3Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-49779
At a glance
CVE-2026-49779 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Tax Exempt for WooCommerce WordPress plugin, affecting versions <= 1.9.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Customer level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2026, reported by Saad Malik.
Vulnerability Overview
The Tax Exempt for WooCommerce plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.9.3. This makes it possible for authenticated attackers, with Custom-level access and above, to perform actions on files outside of the originally intended directory.
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')
Reaching this weakness in Tax Exempt for WooCommerce <= 1.9.3 takes an account at Customer 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. No fixed build of this plugin is recorded for Tax Exempt for WooCommerce yet, so installs running <= 1.9.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Customer 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C