parisneo lollms-webui API Endpoint /uninstall/{app_name} check_access critical step in authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in parisneo lollms-webui. It has been classified as problematic. The impacted element is the function check_access of the file /uninstall/{app_name} of the component API Endpoint. Performing a manipulation results in critical step in authentication.
This vulnerability is reported as CVE-2024-9919. The attack requires a local approach. No exploit exists.
Details
A vulnerability was found in parisneo lollms-webui (unknown version). It has been classified as problematic. This affects the function check_access of the file /uninstall/{app_name} of the component API Endpoint. The manipulation with an unknown input leads to a critical step in authentication vulnerability. CWE is classifying the issue as CWE-304. The product implements an authentication technique, but it skips a step that weakens the technique. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A missing authentication check in the uninstall endpoint of parisneo/lollms-webui V13 allows attackers to perform unauthorized directory deletions. The /uninstall/{app_name} API endpoint does not call the check_access() function to verify the client_id, enabling attackers to delete directories without proper authentication.
The advisory is shared at huntr.com. This vulnerability is uniquely identified as CVE-2024-9919 since 10/13/2024. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.4
CNA Vector (@huntr_ai): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Critical step in authenticationCWE: CWE-304
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/13/2024 🔍03/20/2025 🔍
03/20/2025 🔍
07/09/2025 🔍
Sources
Advisory: huntr.comStatus: Not defined
CVE: CVE-2024-9919 (🔍)
GCVE (CVE): GCVE-0-2024-9919
GCVE (VulDB): GCVE-100-300417
Entry
Created: 03/20/2025 15:12Updated: 07/09/2025 18:22
Changes: 03/20/2025 15:12 (62), 07/09/2025 18:22 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.