CVE-2021-39347 Vulnerability Analysis & Exploit Details

CVE-2021-39347
Vulnerability Scoring

4.3
/10
Medium Risk

The vulnerability CVE-2021-39347 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2021-39347 Details

Status: Modified

Last updated: 🕕 21 Nov 2024, 06:19 UTC
Originally published on: 🕕 04 Oct 2021, 18:15 UTC

Time between publication and last update: 1143 days

CVSS Release: version 3

CVSS3 Source

security@wordfence.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2021-39347 Vulnerability Summary

CVE-2021-39347: 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.

Assessing the Risk of CVE-2021-39347

Access Complexity Graph

The exploitability of CVE-2021-39347 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2021-39347

CVE-2021-39347 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2021-39347, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2021-39347, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2021-39347 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2021-39347 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2021-39347 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.05% (probability of exploit)

EPSS Percentile: 22.55% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 77.45% of others.

CVE-2021-39347 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.10:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.0.10:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.1.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.10:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.10:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.11:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.11:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.12:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.12:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.13:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.13:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.14:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.14:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.15:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.2.15:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paymentplugins:stripe_for_woocommerce:3.3.9:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2021-39347: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...