Search
Search Results (372510 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2024-24028 | 1 Likeshop | 1 Likeshop | 2025-06-17 | 5.9 Medium |
| Server Side Request Forgery (SSRF) vulnerability in Likeshop before 2.5.7 allows attackers to view sensitive information via the avatar parameter in function UserLogic::updateWechatInfo. | ||||
| CVE-2021-23814 | 1 Unisharp | 1 Laravel-filemanager | 2025-06-17 | 6.7 Medium |
| This affects versions of the package unisharp/laravel-filemanager before 2.6.2. The upload() function does not sufficiently validate the file type when uploading. An attacker may be able to reproduce the following steps: 1. Install a package with a web Laravel application. 2. Navigate to the Upload window 3. Upload an image file, then capture the request 4. Edit the request contents with a malicious file (webshell) 5. Enter the path of file uploaded on URL - Remote Code Execution **Note:** Prevention for bad extensions can be done by using a whitelist in the config file(lfm.php). Corresponding document can be found in [here](https://unisharp.github.io/laravel-filemanager/configfolder-categories). | ||||
| CVE-2024-47196 | 1 Siemens | 2 Modelsim, Questa | 2025-06-17 | 6.7 Medium |
| A vulnerability has been identified in ModelSim (All versions < V2025.2), Questa (All versions < V2025.2). vsimk.exe in affected applications allows a specific tcl file to be loaded from the current working directory. This could allow an authenticated local attacker to inject arbitrary code and escalate privileges in installations where administrators or processes with elevated privileges launch vsimk.exe from a user-writable directory. | ||||
| CVE-2022-45699 | 1 Apsystems | 2 Ecu-r, Ecu-r Firmware | 2025-06-17 | 9.8 Critical |
| Command injection in the administration interface in APSystems ECU-R version 5203 allows a remote unauthenticated attacker to execute arbitrary commands as root using the timezone parameter. | ||||
| CVE-2025-3494 | 2025-06-17 | N/A | ||
| This CVE ID has been rejected by its CNA as it was not a security issue. | ||||
| CVE-2025-3493 | 2025-06-17 | N/A | ||
| This CVE ID has been rejected by its CNA as it was not a security issue. | ||||
| CVE-2025-52445 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52444 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52443 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52442 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52441 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52440 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52439 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52438 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2025-52437 | 2025-06-17 | N/A | ||
| Not used | ||||
| CVE-2024-45380 | 2025-06-17 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues during 2024. | ||||
| CVE-2024-45069 | 2025-06-17 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues during 2024. | ||||
| CVE-2024-45065 | 2025-06-17 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues during 2024. | ||||
| CVE-2024-43422 | 2025-06-17 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues during 2024. | ||||
| CVE-2024-21856 | 2025-06-17 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues during 2024. | ||||