WooCommerce <= 6.2.0 - Path Traversal via Tax Importer

2022-02-22 00:00
Anonymous

Strategic Overview

Status
Patched in 6.2.1
Affected Plugin
WooCommerce
Affected Version
<= 6.2.0
CVSS
7.2High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE pending
View all WooCommerce vulnerabilities

At a glance

This record tracks a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WooCommerce WordPress plugin, affecting versions <= 6.2.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 6.2.1; sites on affected versions should update now. Disclosed February 2022.

Vulnerability Overview

The WooCommerce plugin for WordPress is vulnerable to path traversal via the 'file_url' parameter found in the importers functionality in versions up to, and including, 6.2.0. This makes it possible for authenticated attackers, with high-level permissions such as an administrator, to access files outside of the intended directory when performing an import.

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, integrity, availability — full site compromise territory.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

WooCommerce <= 6.2.0 carries this weakness at file_url, and reaching it takes a caller who can reach the endpoint. 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 WooCommerce the fix is 6.2.1: builds <= 6.2.0 are affected, anything from 6.2.1 onward is not.

Remediation

Update to version 6.2.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WooCommerce 6.2.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/5cbf597e-7a2f-416c-8969-3679b487f57a

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C