WooCommerce <= 4.0.4 - Unauthorized Post Meta Creation/Modification

2020-05-05 00:00

Strategic Overview

Status: Patched in 4.1.0
Affected Plugin: WooCommerce
Affected Version: < 4.1.0
CVSS: 8.8High
Weakness type: CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE: CVE pending

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WooCommerce WordPress plugin, affecting versions < 4.1.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 4.1.0; sites on affected versions should update now. Disclosed May 2020, reported by Slavco Mihajloski.

Vulnerability Overview

The WooCommerce plugin for WordPress is vulnerable to arbitrary product meta data creation/overwriting due to a lack of escaping and validation on the post meta data being supplied during product duplication in versions up to, and including 4.0.4. This makes it possible for authenticated attackers, with product duplicating capabilities, to modify post meta that could potential be used to achieve remote code execution.

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-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in WooCommerce < 4.1.0 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WooCommerce the fix is 4.1.0: builds < 4.1.0 are affected, anything from 4.1.0 onward is not.

Remediation

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

Firewall
Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/c232b39c-7144-4d3a-9770-883986ca8b29

Related records

Same weakness class

Other vulnerabilities in WooCommerce

CVSS Vector

8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/