WooCommerce <= 3.6.4 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2019-07-02 00:00

Strategic Overview

Status: Patched in 3.6.5
Affected Plugin: WooCommerce
Affected Version: < 3.6.5
CVSS: 8.8High
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE pending

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WooCommerce WordPress plugin, affecting versions < 3.6.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.6.5; sites on affected versions should update now. Disclosed July 2019, reported by DENNIS BRINKROLF.

Vulnerability Overview

The WooCommerce plugin for WordPress is vulnerable to Cross-Site Request forgery in versions up to, and including 3.6.4, due to the CSV importer actions missing a nonce validation. This makes it possible for attackers with at least author privileges to embed script code in a CSV, upload it to the target site, and then trick an administrator into uploading the CSV injected payload to a product description via a forged request all granted they can trick them into performing an action such as clicking on a link.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WooCommerce < 3.6.5 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WooCommerce the fix is 3.6.5: builds < 3.6.5 are affected, anything from 3.6.5 onward is not.

Remediation

Update to version 3.6.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. None of that substitutes for the fix: WooCommerce 3.6.5 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/2edb574d-74b7-4f72-91a1-bb6632709b7a

Related records

Same weakness class

Other vulnerabilities in WooCommerce

CVSS Vector

8.8

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
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/