CVE-2021-34619

WooCommerce Stock Manager <= 2.5.7 - Cross-Site Request Forgery to Arbitrary File Upload

2021-06-14 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 2.6.0
Affected Version
<= 2.5.7
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-34619
View all Stock Manager for WooCommerce vulnerabilities

At a glance

CVE-2021-34619 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Stock Manager for WooCommerce WordPress plugin, affecting versions <= 2.5.7. 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 2.6.0; sites on affected versions should update now. Disclosed June 2021, reported by Chloe Chamberland.

Vulnerability Overview

The WooCommerce Stock Manager WordPress plugin is vulnerable to Cross-Site Request Forgery leading to Arbitrary File Upload in versions up to, and including, 2.5.7 due to missing nonce and file validation in the /woocommerce-stock-manager/trunk/admin/views/import-export.php file.

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 Stock Manager for WooCommerce <= 2.5.7 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 Stock Manager for WooCommerce the fix is 2.6.0: builds <= 2.5.7 are affected, anything from 2.6.0 onward is not.

Remediation

Update to version 2.6.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Stock Manager for WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Stock Manager for WooCommerce 2.6.0 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