CVE-2023-34092 Vulnerability Analysis & Exploit Details

CVE-2023-34092
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2023-34092 poses a critical security risk that could lead to severe breaches.

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-34092 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:06 UTC
Originally published on: 🕔 01 Jun 2023, 17:15 UTC

Time between publication and last update: 538 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-34092 Vulnerability Summary

CVE-2023-34092: Vite provides frontend tooling. Prior to versions 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, and 4.3.9, Vite Server Options (`server.fs.deny`) can be bypassed using double forward-slash (//) allows any unauthenticated user to read file from the Vite root-path of the application including the default `fs.deny` settings (`['.env', '.env.*', '*.{crt,pem}']`). Only users explicitly exposing the Vite dev server to the network (using `--host` or `server.host` config option) are affected, and only files in the immediate Vite project root folder could be exposed. This issue is fixed in vite@4.3.9, vite@4.2.3, vite@4.1.5, vite@4.0.5, vite@3.2.7, and vite@2.9.16.

Assessing the Risk of CVE-2023-34092

Access Complexity Graph

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

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

  • Confidentiality: High
    Exploiting CVE-2023-34092 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2023-34092 poses no threat to data integrity.
  • Availability: None
    CVE-2023-34092 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.18% (probability of exploit)

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

CVE-2023-34092 References

External References

CWE Common Weakness Enumeration

CWE-706

CAPEC Common Attack Pattern Enumeration and Classification

  • Redirect Access to Libraries CAPEC-159 An adversary exploits a weakness in the way an application searches for external libraries to manipulate the execution flow to point to an adversary supplied library or code base. This pattern of attack allows the adversary to compromise the application or server via the execution of unauthorized code. An application typically makes calls to functions that are a part of libraries external to the application. These libraries may be part of the operating system or they may be third party libraries. If an adversary can redirect an application's attempts to access these libraries to other libraries that the adversary supplies, the adversary will be able to force the targeted application to execute arbitrary code. This is especially dangerous if the targeted application has enhanced privileges. Access can be redirected through a number of techniques, including the use of symbolic links, search path modification, and relative path manipulation.
  • Create files with the same name as files protected with a higher classification CAPEC-177 An attacker exploits file location algorithms in an operating system or application by creating a file with the same name as a protected or privileged file. The attacker could manipulate the system if the attacker-created file is trusted by the operating system or an application component that attempts to load the original file. Applications often load or include external files, such as libraries or configuration files. These files should be protected against malicious manipulation. However, if the application only uses the name of the file when locating it, an attacker may be able to create a file with the same name and place it in a directory that the application will search before the directory with the legitimate file is searched. Because the attackers' file is discovered first, it would be used by the target application. This attack can be extremely destructive if the referenced file is executable and/or is granted special privileges based solely on having a particular name.
  • Passing Local Filenames to Functions That Expect a URL CAPEC-48 This attack relies on client side code to access local files and resources instead of URLs. When the client browser is expecting a URL string, but instead receives a request for a local file, that execution is likely to occur in the browser process space with the browser's authority to local files. The attacker can send the results of this request to the local files out to a site that they control. This attack may be used to steal sensitive authentication data (either local or remote), or to gain system profile information to launch further attacks.
  • DLL Side-Loading CAPEC-641 An adversary places a malicious version of a Dynamic-Link Library (DLL) in the Windows Side-by-Side (WinSxS) directory to trick the operating system into loading this malicious DLL instead of a legitimate DLL. Programs specify the location of the DLLs to load via the use of WinSxS manifests or DLL redirection and if they aren't used then Windows searches in a predefined set of directories to locate the file. If the applications improperly specify a required DLL or WinSxS manifests aren't explicit about the characteristics of the DLL to be loaded, they can be vulnerable to side-loading.

Vulnerable Configurations

  • cpe:2.3:a:vitejs:vite:3.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.0.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.0.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.0:beta0:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.0:beta0:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.0:beta0:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.0:beta0:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.0:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.0:beta4:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:3.2.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:3.2.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta0:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta0:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta4:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta5:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta5:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta6:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta6:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:beta7:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:beta7:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:alpha0:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:alpha0:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:alpha1:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:alpha2:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:alpha2:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:alpha3:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:alpha3:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:alpha4:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:alpha4:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:alpha5:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:alpha5:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.0:alpha6:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.0:alpha6:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.0:beta0:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.0:beta0:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.2.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.2.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.2.0:beta0:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.2.0:beta0:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.2.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.2.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.2.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.2.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta0:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta0:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta4:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta5:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta5:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta6:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta6:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta7:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta7:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.0:beta8:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.0:beta8:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:4.3.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:4.3.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vitejs:vite:2.9.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:vitejs:vite:2.9.15:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2023-34092: 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...