CVE-2016-10112

WooCommerce <= 2.6.8 - Authenticated Stored Cross-Site Scripting

2016-12-07 00:00
Anonymous

Strategic Overview

Status
Patched in 2.6.9
Affected Plugin
WooCommerce
Affected Version
< 2.6.9
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2016-10112
View all WooCommerce vulnerabilities

At a glance

CVE-2016-10112 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WooCommerce WordPress plugin, affecting versions < 2.6.9. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.6.9; sites on affected versions should update now. Disclosed December 2016.

Vulnerability Overview

Cross-site scripting (XSS) vulnerability in the WooCommerce plugin before 2.6.9 for WordPress allows remote authenticated administrators to inject arbitrary web script or HTML by providing crafted tax-rate table values in CSV format.

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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WooCommerce < 2.6.9 takes any authenticated account. 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.6.9: builds < 2.6.9 are affected, anything from 2.6.9 onward is not.

Remediation

Update to version 2.6.9, 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.6.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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