CVE-2021-39347

Stripe for WooCommerce 3.0.0 - 3.3.9 - Missing Authorization Controls to Financial Account Hijacking

2021-10-01 15:29

Strategic Overview

Status: Patched in 3.3.10
Affected Plugin: Stripe for WooCommerce
Affected Version: 3.0.0 – 3.3.9
CVSS: 4.3Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2021-39347

View all Stripe for WooCommerce vulnerabilities

At a glance

CVE-2021-39347 is a medium-severity Missing Authorization vulnerability in the Stripe for WooCommerce WordPress plugin, affecting versions 3.0.0 – 3.3.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.3.10; sites on affected versions should update now. Disclosed October 2021, reported by Margaux DABERT.

Vulnerability Overview

The Stripe for WooCommerce WordPress plugin is missing a capability check on the save() function found in the ~/includes/admin/class-wc-stripe-admin-user-edit.php file that makes it possible for attackers to configure their account to use other site users unique STRIPE identifier and make purchases with their payment accounts. This affects versions 3.0.0 - 3.3.9.

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.

CWE-862: Missing Authorization

Stripe for WooCommerce 3.0.0 – 3.3.9 carries this weakness at save(), and reaching it 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 Stripe for WooCommerce the fix is 3.3.10: builds 3.0.0 – 3.3.9 are affected, anything from 3.3.10 onward is not.

Remediation

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

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-39347 https://www.wordfence.com/threat-intel/vulnerabilities/id/7f706c15-56c8-4eb4-9790-b394d37b0e33 https://nvd.nist.gov/vuln/detail/CVE-2021-39347

CVSS Vector

4.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE 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 Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

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/