WooCommerce <= 3.4.4 - Authenticated PHP Object Injection

2018-08-29 00:00
Anonymous

Strategic Overview

Status
Patched in 3.4.5
Affected Plugin
WooCommerce
Affected Version
< 3.4.5
CVSS
6.6Medium
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE pending
View all WooCommerce vulnerabilities

At a glance

This record tracks a medium-severity Deserialization of Untrusted Data vulnerability in the WooCommerce WordPress plugin, affecting versions < 3.4.5. It carries a CVSS score of 6.6 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 3.4.5; sites on affected versions should update now. Disclosed August 2018.

Vulnerability Overview

The WooCommerce plugin for WordPress is vulnerable to PHP Object Injection by users with access to edit attributes in versions up to, and including 3.4.4.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Reaching this weakness in WooCommerce < 3.4.5 takes any authenticated account. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For WooCommerce the fix is 3.4.5: builds < 3.4.5 are affected, anything from 3.4.5 onward is not.

Remediation

Update to version 3.4.5, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WooCommerce 3.4.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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