CVE-2023-41875 Vulnerability Analysis & Exploit Details

CVE-2023-41875
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2023-41875 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-2023-41875 Details

Status: Analyzed

Last updated: 🕝 27 Feb 2025, 02:45 UTC
Originally published on: 🕒 13 Dec 2024, 15:15 UTC

Time between publication and last update: 75 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-2023-41875 Vulnerability Summary

CVE-2023-41875: Missing Authorization vulnerability in wpdirectorykit.com WP Directory Kit allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Directory Kit: from n/a through 1.2.6.

Assessing the Risk of CVE-2023-41875

Access Complexity Graph

The exploitability of CVE-2023-41875 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-2023-41875

With low attack complexity and no required privileges, CVE-2023-41875 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-2023-41875, 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-2023-41875, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

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

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

CVE-2023-41875 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:wpdirectorykit:wp_directory_kit:1.0.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.0.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.1.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:wpdirectorykit:wp_directory_kit:1.2.6:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2023-41875: 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-27636 – Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from ...
  • CVE-2025-2121 – A vulnerability classified as critical has been found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected is an unknown function of the comp...
  • CVE-2025-2120 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been rated as problematic. This issue affects some unknown proce...
  • CVE-2025-2119 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been declared as problematic. This vulnerability affects unknown...
  • CVE-2025-2118 – A vulnerability was found in Quantico Tecnologia PRMV 6.48. It has been classified as critical. This affects an unknown part of the file /admin/log...