CVE-2018-17605 Vulnerability Analysis & Exploit Details

CVE-2018-17605
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2018-17605 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-2018-17605 Details

Status: Modified

Last updated: 🕞 21 Nov 2024, 03:54 UTC
Originally published on: 🕘 28 Sep 2018, 09:29 UTC

Time between publication and last update: 2245 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2018-17605 Vulnerability Summary

CVE-2018-17605: An issue was discovered in the Asset Pipeline plugin before 3.0.4 for Grails. An attacker can perform directory traversal via a crafted request when a servlet-based application is executed in Jetty, because there is a classloader vulnerability that can allow a reverse file traversal route in AssetPipelineFilter.groovy or AssetPipelineFilterCore.groovy.

Assessing the Risk of CVE-2018-17605

Access Complexity Graph

The exploitability of CVE-2018-17605 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-2018-17605

With low attack complexity and no required privileges, CVE-2018-17605 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-2018-17605, 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-2018-17605, 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-2018-17605 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2018-17605 poses no threat to data integrity.
  • Availability: None
    CVE-2018-17605 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.127% (probability of exploit)

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

CVE-2018-17605 References

External References

CWE Common Weakness Enumeration

CWE-22

CAPEC Common Attack Pattern Enumeration and Classification

  • Path Traversal CAPEC-126 An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
  • Using Slashes and URL Encoding Combined to Bypass Validation Logic CAPEC-64 This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
  • Manipulating Web Input to File System Calls CAPEC-76 An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
  • Using Escaped Slashes in Alternate Encoding CAPEC-78 This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • Using Slashes in Alternate Encoding CAPEC-79 This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.

Vulnerable Configurations

  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:0.6.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:0.6.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:0.6.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:0.6.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.10:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.10:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.16:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.16:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.17:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.0.17:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.1.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.1.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.1.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.1.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.5:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.2.5:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.7:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.7:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.8:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.3.8:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.4.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.8:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.5.8:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.7:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.7:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.9:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.6.9:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.7.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.7.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.7.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.7.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.7.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.7.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.8.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.8.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.8.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.8.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.8.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.8.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.9.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.10.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.5:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.5:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.6:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.11.6:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.5:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.5:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.6:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.6:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.7:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.7:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.8:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.8:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.9:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.12.9:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.13.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.13.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.13.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.13.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.13.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.13.2:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.3:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.3:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.4:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.4:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.7:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.7:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.10:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.14.10:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.15.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.15.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.15.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:2.15.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:3.0.0:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:3.0.0:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:3.0.1:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:3.0.1:*:*:*:*:grails:*:*
  • cpe:2.3:a:asset_pipeline_project:asset-pipeline:3.0.2:*:*:*:*:grails:*:*
    cpe:2.3:a:asset_pipeline_project:asset-pipeline:3.0.2:*:*:*:*:grails:*:*

Protect Your Infrastructure against CVE-2018-17605: 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-3801 – A vulnerability was found in songquanpeng one-api up to 0.6.10. It has been classified as problematic. This affects an unknown part of the componen...
  • CVE-2025-3800 – A vulnerability has been found in WCMS 11 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app/co...
  • CVE-2025-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...
  • CVE-2025-3798 – A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminCon...
  • CVE-2025-3661 – The SB Chart block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and inclu...