Authenticated payment-account misuse via unchecked customer identifier update
Published Oct 4, 2021 · Updated Mar 31, 2025
Missing authorization in Stripe for WooCommerce 3.0.0 through 3.3.9 allows remote authenticated users to charge another user's payment account. The save() method in includes/admin/class-wc-stripe-admin-user-edit.php accepts and stores a user-supplied Stripe customer identifier without a capability check. Any logged-in account that can reach the profile update path can associate itself with another site user's identifier and make purchases against that linked payment account.
Summary
What happened
Missing authorization in Stripe for WooCommerce 3.0.0 through 3.3.9 allows remote authenticated users to charge another user's payment account. The save() method in includes/admin/class-wc-stripe-admin-user-edit.php accepts and stores a user-supplied Stripe customer identifier without a capability check. Any logged-in account that can reach the profile update path can associate itself with another site user's identifier and make purchases against that linked payment account.
The record
- CVE
- CVE-2021-39347
- Published
- Oct 4, 2021
- Updated
- Mar 31, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1657
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2021CVE publishedPublication date reported by the CVE source.
- Mar 31, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo