WooCommerce <= 4.6.1 & WooCommerce Blocks <= 3.7.0 - Settings Bypass leading to Account Creation

2020-11-05 00:00
Anonymous

Strategic Overview

Status
Patched in 3.7.1
Affected Plugin
WooCommerce Blocks
Affected Version
< 3.7.1
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all WooCommerce Blocks vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the WooCommerce Blocks WordPress plugin, affecting versions < 3.7.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.1; sites on affected versions should update now. Disclosed November 2020.

Vulnerability Overview

The WooCommerce plugin for WordPress is vulnerable to unauthorized user account creation during checkout even when the “Allow customers to create an account during checkout” setting is disabled. was disabled due to missing authorization checks in versions up to and including 4.6.1. The WooCommerce Blocks plugin for WordPress is vulnerable to the same issue in versions up to, and including, 3.7.1.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WooCommerce Blocks < 3.7.1 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WooCommerce Blocks the fix is 3.7.1: builds < 3.7.1 are affected, anything from 3.7.1 onward is not.

Remediation

Update to version 3.7.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WooCommerce Blocks 3.7.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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