WooCommerce < 5.7.0 & WooCommerce Admin < 2.6.4 - Information Disclosure
Strategic Overview
- Status
- Patched in 4.0.3
- Affected Plugin
- WooCommerce
- Affected Version
4.0 – < 5.6.1 · 18 branches- CVSS
- 6.5Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE pending
At a glance
This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WooCommerce WordPress plugin, affecting versions 4.0 – < 5.6.1 · 18 branches. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.3; sites on affected versions should update now. Disclosed April 2022.
Vulnerability Overview
The WooCommerce and WooCommerce Admin plugins for WordPress are vulnerable to Sensitive Data Exposure in versions up to 5.7.0 for WooCommerce and 2.6.4 for WooCommerce Admin due to insufficient protection of analytic report storage in the directory they are stored. This makes it possible for attackers to extract sensitive data related to report analytics on certain host configurations.
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 privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WooCommerce 4.0 – < 5.6.1 · 18 branches takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WooCommerce the fix is 4.0.3: builds 4.0 – < 5.6.1 · 18 branches are affected, anything from 4.0.3 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 4.0.3, 4.1.3, 4.2.4, 4.3.5, 4.4.3, 4.5.4, 4.6.4, 4.7.3, 4.8.2, 4.9.4, 5.0.2, 5.1.2, 5.2.4, 5.3.2, 5.4.3, 5.5.3, 5.6.1, 5.7.0
How does WordSec protect against this?
The fix is the thing that ends this: WooCommerce 4.0.3 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WooCommerce
- 8.8CVE-2021-32790: WooCommerce < 5.5 Blind SQL Injection
CVE-2021-32790 - 8.8WooCommerce <= 4.0.4 Unauthorized Post Meta Creation/Modification
- 8.8WooCommerce <= 3.6.4 CSRF to Stored Cross-Site Scripting
- 8.8CVE-2017-18356: WooCommerce <= 3.2.3 PHP Object Injection
CVE-2017-18356 - 7.5CVE-2026-48888: WooCommerce < 11.1.0 Denial of Service
CVE-2026-48888 - 7.5WooCommerce <= 2.3.10 PHP Object Injection
- 7.3CVE-2014-6313: WooCommerce <= 2.2.2 Cross-Site Scripting
CVE-2014-6313 - 7.2WooCommerce <= 6.2.0 Path Traversal via Tax Importer
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C