Export limit exceeded: 375210 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (375210 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2024-2288 | 1 Lollms | 1 Lollms Web Ui | 2025-10-15 | 8.3 High |
| A Cross-Site Request Forgery (CSRF) vulnerability exists in the profile picture upload functionality of the Lollms application, specifically in the parisneo/lollms-webui repository, affecting versions up to 7.3.0. This vulnerability allows attackers to change a victim's profile picture without their consent, potentially leading to a denial of service by overloading the filesystem with files. Additionally, this flaw can be exploited to perform a stored cross-site scripting (XSS) attack, enabling attackers to execute arbitrary JavaScript in the context of the victim's browser session. The issue is resolved in version 9.3. | ||||
| CVE-2024-10950 | 1 Binary-husky | 1 Gpt Academic | 2025-10-15 | N/A |
| In binary-husky/gpt_academic version <= 3.83, the plugin `CodeInterpreter` is vulnerable to code injection caused by prompt injection. The root cause is the execution of user-provided prompts that generate untrusted code without a sandbox, allowing the execution of parts of the LLM-generated code. This vulnerability can be exploited by an attacker to achieve remote code execution (RCE) on the application backend server, potentially gaining full control of the server. | ||||
| CVE-2024-10819 | 1 Binary-husky | 1 Gpt Academic | 2025-10-15 | 8.8 High |
| A Cross-Site Request Forgery (CSRF) vulnerability in version 3.83 of binary-husky/gpt_academic allows an attacker to trick a user into uploading files without their consent, exploiting their session. This can lead to unauthorized file uploads and potential system compromise. The uploaded file can contain malicious scripts, leading to stored Cross-Site Scripting (XSS) attacks. Through stored XSS, an attacker can steal information about the victim and perform any action on their behalf. | ||||
| CVE-2024-10481 | 1 Comfy | 1 Comfyui | 2025-10-15 | N/A |
| A CSRF vulnerability exists in comfyanonymous/comfyui versions up to v0.2.2. This vulnerability allows attackers to host malicious websites that, when visited by authenticated ComfyUI users, can perform arbitrary API requests on behalf of the user. This can be exploited to perform actions such as uploading arbitrary files via the `/upload/image` endpoint. The lack of CSRF protections on API endpoints like `/upload/image`, `/prompt`, and `/history` leaves users vulnerable to unauthorized actions, which could be combined with other vulnerabilities such as stored-XSS to further compromise user sessions. | ||||
| CVE-2024-10252 | 1 Langgenius | 1 Dify | 2025-10-15 | 7.2 High |
| A vulnerability in langgenius/dify versions <=v0.9.1 allows for code injection via internal SSRF requests in the Dify sandbox service. This vulnerability enables an attacker to execute arbitrary Python code with root privileges within the sandbox environment, potentially leading to the deletion of the entire sandbox service and causing irreversible damage. | ||||
| CVE-2024-5133 | 1 Lunary | 1 Lunary | 2025-10-15 | 8.1 High |
| In lunary-ai/lunary version 1.2.4, an account takeover vulnerability exists due to the exposure of password recovery tokens in API responses. Specifically, when a user initiates the password reset process, the recovery token is included in the response of the `GET /v1/users/me/org` endpoint, which lists all users in a team. This allows any authenticated user to capture the recovery token of another user and subsequently change that user's password without consent, effectively taking over the account. The issue lies in the inclusion of the `recovery_token` attribute in the users object returned by the API. | ||||
| CVE-2025-62448 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62447 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62446 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62445 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62444 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62443 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62442 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62441 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-62440 | 2025-10-15 | N/A | ||
| Not used | ||||
| CVE-2025-40615 | 1 Bookgy | 1 Bookgy | 2025-10-14 | 6.1 Medium |
| Reflected Cross-Site Scripting (XSS) vulnerability in Bookgy. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending a malicious URL through the "TEXTO" parameter in /api/api_ajustes.php. | ||||
| CVE-2025-40616 | 1 Bookgy | 1 Bookgy | 2025-10-14 | 6.1 Medium |
| Reflected Cross-Site Scripting (XSS) vulnerability in Bookgy. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending a malicious URL through the "IDRESERVA" parameter in /bkg_imprimir_comprobante.php. | ||||
| CVE-2025-40617 | 1 Bookgy | 1 Bookgy | 2025-10-14 | 9.8 Critical |
| SQL injection vulnerability in Bookgy. This vulnerability could allow an attacker to retrieve, create, update and delete databases by sending an HTTP request through the "IDTIPO", "IDPISTA" and "IDSOCIO" parameters in /bkg_seleccionar_hora_ajax.php. | ||||
| CVE-2025-40618 | 1 Bookgy | 1 Bookgy | 2025-10-14 | 9.8 Critical |
| SQL injection vulnerability in Bookgy. This vulnerability could allow an attacker to retrieve, create, update and delete databases by sending an HTTP request through the "IDRESERVA" parameter in /bkg_imprimir_comprobante.php | ||||
| CVE-2025-40619 | 1 Bookgy | 1 Bookgy | 2025-10-14 | 7.5 High |
| Bookgy does not provide for proper authorisation control in multiple areas of the application. This deficiency could allow a malicious actor, without authentication, to reach private areas and/or areas intended for other roles. | ||||