CVE-2022-33901 Vulnerability Analysis & Exploit Details

CVE-2022-33901
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2022-33901 presents a notable risk, potentially requiring prompt mitigation.

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: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-33901 Details

Status: Modified

Last updated: 🕘 20 Feb 2025, 21:15 UTC
Originally published on: 🕔 22 Jul 2022, 17:15 UTC

Time between publication and last update: 944 days

CVSS Release: version 3

CVSS3 Source

audit@patchstack.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-33901 Vulnerability Summary

CVE-2022-33901: Unauthenticated Arbitrary File Read vulnerability in MultiSafepay plugin for WooCommerce plugin <= 4.13.1 at WordPress.

Assessing the Risk of CVE-2022-33901

Access Complexity Graph

The exploitability of CVE-2022-33901 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-2022-33901

With low attack complexity and no required privileges, CVE-2022-33901 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-2022-33901, 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-2022-33901, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2022-33901 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2022-33901 poses no threat to data integrity.
  • Availability: None
    CVE-2022-33901 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: 1.75% (probability of exploit)

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

CVE-2022-33901 References

External References

CWE Common Weakness Enumeration

CWE-552

CAPEC Common Attack Pattern Enumeration and Classification

  • Collect Data from Common Resource Locations CAPEC-150 An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks.
  • Probe System Files CAPEC-639 An adversary obtains unauthorized information due to improperly protected files. If an application stores sensitive information in a file that is not protected by proper access control, then an adversary can access the file and search for sensitive information.

Vulnerable Configurations

  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:-:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:-:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.2.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.2.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.3.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.3.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.4.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.4.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.5.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.5.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.5.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.5.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.5.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.5.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.6.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.6.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.6.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.6.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.7.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.7.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.8.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:3.8.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.1.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.2.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.2.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.2.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.2.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.3.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.3.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.4.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.4.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.4.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.4.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.5.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.5.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.5.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.5.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.6.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.6.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.7.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.7.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.8.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.9.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.9.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.10.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.10.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.11.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.11.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.12.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.12.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.13.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.13.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.13.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.13.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.14.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.14.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.15.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:multisafepay:multisafepay_plugin_for_woocommerce:4.15.0:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2022-33901: 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-2025-4249 – A vulnerability was found in PHPGurukul e-Diary Management System 1.0 and classified as critical. Affected by this issue is some unknown functional...
  • CVE-2025-4248 – A vulnerability has been found in SourceCodester Simple To-Do List System 1.0 and classified as critical. Affected by this vulnerability is an unkn...
  • CVE-2025-4247 – A vulnerability, which was classified as critical, was found in SourceCodester Simple To-Do List System 1.0. Affected is an unknown function of the...
  • CVE-2025-47245 – In BlueWave Checkmate through 2.0.2 before d4a6072, an invite request can be modified to specify a privileged role.
  • CVE-2025-47244 – Inedo ProGet through 2024.22 allows remote attackers to reach restricted functionality through the C# reflection layer, as demonstrated by causing ...