WooCommerce Subscriptions <= 3.0.2 - Cross-Site Request Forgery

2020-04-02 00:00
Dewhurst Security

Strategic Overview

Status
Patched in 3.0.3
Affected Plugin
WooCommerce Subscription
Affected Version
< 3.0.3
CVSS
8.3High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all WooCommerce Subscription vulnerabilities

At a glance

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

Vulnerability Overview

The WooCommerce Subscriptions plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.0.2. This is due to incorrect nonce validation on the view-subscription functionality. This makes it possible for unauthenticated attackers to modify any user's subscription status via a forged request granted they can trick a site administrator 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.

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

Reaching this weakness in WooCommerce Subscription < 3.0.3 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 Subscription the fix is 3.0.3: builds < 3.0.3 are affected, anything from 3.0.3 onward is not.

Remediation

Update to version 3.0.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WooCommerce Subscription: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WooCommerce Subscription 3.0.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/dbc98f55-a8f9-4234-84aa-df38302bf0b8

Related records

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