CVE-2023-25986 Vulnerability Analysis & Exploit Details

CVE-2023-25986
Vulnerability Scoring

4.3
/10
Medium Risk

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

CVE-2023-25986 Details

Status: Modified

Last updated: 🕢 21 Nov 2024, 07:50 UTC
Originally published on: 🕕 22 Nov 2023, 18:15 UTC

Time between publication and last update: 364 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:R/S:U/C:N/I:L/A:N

CVE-2023-25986 Vulnerability Summary

CVE-2023-25986: Cross-Site Request Forgery (CSRF) vulnerability in WattIsIt PayGreen – Ancienne version plugin <= 4.10.2 versions.

Assessing the Risk of CVE-2023-25986

Access Complexity Graph

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

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

  • Confidentiality: None
    CVE-2023-25986 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2023-25986 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2023-25986 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.087% (probability of exploit)

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

CVE-2023-25986 References

External References

CWE Common Weakness Enumeration

CWE-352

CAPEC Common Attack Pattern Enumeration and Classification

  • JSON Hijacking (aka JavaScript Hijacking) CAPEC-111 An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website.
  • Cross-Domain Search Timing CAPEC-462 An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain.
  • Cross Site Identification CAPEC-467 An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the "remember me" feature to keep their session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing).
  • Cross Site Request Forgery CAPEC-62 An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.

Vulnerable Configurations

  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.9:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.10:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.10:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.11:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.11:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.12:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.12:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.13:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.13:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.14:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.14:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.15:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.15:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.16:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.16:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.17:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.17:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.18:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.18:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.19:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.0.19:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:3.2.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.0.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.2.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.2.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.2.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.2.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.3.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.3.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.4.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.4.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.4.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.4.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.4.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.4.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.5.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.5.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.6.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.6.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.6.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.6.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.6.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.6.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.7.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.7.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.8.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.9.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.9.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.10.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.10.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.10.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.10.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:paygreen:paygreen_-_ancienne:4.10.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:paygreen:paygreen_-_ancienne:4.10.2:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2023-25986: 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-46328 – snowflake-connector-nodejs is a NodeJS driver for Snowflake. Versions starting from 1.10.0 to before 2.0.4, are vulnerable to a Time-of-Check to Ti...
  • CVE-2025-46327 – gosnowflake is the Snowflake Golang driver. Versions starting from 1.7.0 to before 1.13.3, are vulnerable to a Time-of-Check to Time-of-Use (TOCTOU...
  • CVE-2025-46326 – snowflake-connector-net is the Snowflake Connector for .NET. Versions starting from 2.1.2 to before 4.4.1, are vulnerable to a Time-of-Check to Tim...
  • CVE-2025-4039 – A vulnerability was found in PHPGurukul Rail Pass Management System 1.0. It has been rated as critical. Affected by this issue is some unknown func...
  • CVE-2025-4038 – A vulnerability was found in code-projects Train Ticket Reservation System 1.0. It has been declared as critical. Affected by this vulnerability is...