LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39347: Stripe for WooCommerce 3.0.0 - 3.3.9 Missing Authorization Controls to Financial Account Hijacking

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.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Affected WooCommerce stores could let a logged-in attacker link their account to another user's Stripe identifier, potentially making purchases using that user's payment account. This is not described as full site compromise, but it creates direct financial abuse risk for stores with customer logins.

Executive priority

Treat as a moderate priority for any public WooCommerce store with customer accounts. It is not identified as actively exploited, but payment-account misuse can create financial loss, refunds, chargebacks, and customer trust impact.

Technical view

CVE-2021-39347 is a CWE-862 missing authorization control in the Stripe for WooCommerce plugin save() function in includes/admin/class-wc-stripe-admin-user-edit.php. Versions 3.0.0 through 3.3.9 are affected. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, integrity impact only.

Likely exposure

Exposure is likely limited to WordPress/WooCommerce sites running Stripe for WooCommerce versions 3.0.0 through 3.3.9. Risk is higher where untrusted customers can create or access accounts. Sites not using this plugin, or using versions outside the affected range, are not identified as affected by the supplied sources.

Exploitation context

The supplied sources and KEV status do not show active exploitation. Abuse requires an authenticated low-privilege account and targets Stripe identifier authorization, not unauthenticated code execution. The business impact is payment misuse and transaction integrity loss rather than confidentiality or availability damage.

Researcher notes

Evidence identifies the vulnerable function and affected version range, but the bundle does not provide exploit telemetry or detailed remediation text. Validate by version inventory and data integrity review; avoid assuming broader Stripe, WooCommerce, or WordPress core exposure.

Mitigation direction

  • Upgrade Stripe for WooCommerce beyond the affected 3.0.0-3.3.9 range after checking vendor guidance.
  • Audit user Stripe identifiers for unexpected associations.
  • Review WooCommerce orders for suspicious purchases or payment disputes during the vulnerable period.
  • Limit untrusted account access until the plugin is verified remediated.

Validation and detection

  • Inventory WordPress sites using Stripe for WooCommerce.
  • Confirm installed plugin versions are not 3.0.0 through 3.3.9.
  • Check user records for duplicate or unexpected Stripe identifiers.
  • Review logs and orders for account/payment mismatches.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-39347 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-39347Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Stripe for WooCommerceStripe for WooCommerce3.0.0 - 3.3.9Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.