WooCommerce <= 2.0.17 - Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.0.18
- Affected Plugin
- WooCommerce
- Affected Version
<= 2.0.17- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WooCommerce WordPress plugin, affecting versions <= 2.0.17. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.18; sites on affected versions should update now. Disclosed October 2013, reported by Gjoko Krstic.
Vulnerability Overview
The WooCommerce plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 2.0.17 via the 'hide-wc-extensions-message' parameter due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser session.
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.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
WooCommerce <= 2.0.17 carries this weakness at hide-wc-extensions-message, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WooCommerce the fix is 2.0.18: builds <= 2.0.17 are affected, anything from 2.0.18 onward is not.
Remediation
Update to version 2.0.18, 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 2.0.18 closes this, and updating the plugin is the step that ends it.
- Firewall
- 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.2WooCommerce <= 6.2.0 Path Traversal via Tax Importer
- 7.2WooCommerce <= 3.6.4 Missing File Type Validation
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C