CVE-2024-4841
Lollms-Webui 9.6
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2024-4841 is a low-severity Path Traversal: '\..\filename' (CWE-29) vulnerability in Lollms Lollms-Webui. Its CVSS base score is 3.3 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as LLM Application Platforms; in the Privacy and Disclosure risk domain.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A Path Traversal vulnerability tracked as CVE-2024-4841 affects the parisneo/lollms-webui application in versions v9.6 through the latest release. The flaw resides in the add_reference_to_local_mode function, which fails to sanitize the path parameter supplied in HTTP requests to the /add_reference_to_local_model endpoint, allowing directory traversal under CWE-29. The issue received a CVSS 3.1 score of 3.3 reflecting local attack vector, low complexity, and limited confidentiality impact.
An authenticated local user can exploit the weakness by submitting crafted path values to enumerate folders, subfolders, and files present on the host system. No user interaction is required, and the attack remains confined to information disclosure without direct modification or denial-of-service effects.
The associated EPSS score has stayed low, reaching a peak of 0.0934 and currently sitting at 0.0846. Public details are available in the referenced huntr.com bounty reports.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44422
Vulnerability Data
A Path Traversal vulnerability exists in the parisneo/lollms-webui, specifically within the 'add_reference_to_local_mode' function due to the lack of input sanitization. This vulnerability affects versions v9.6 to the latest. By exploiting this vulnerability, an attacker can predict the folders, subfolders, and…
more
files present on the victim's computer. The vulnerability is present in the way the application handles the 'path' parameter in HTTP requests to the '/add_reference_to_local_model' endpoint.
- CWE(s)
AI Security AnalysisAI
- AI Category
- LLM Application Platforms
- Risk Domain
- Privacy and Disclosure
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- parisneo/lollms-webui is an open-source WebUI platform for running and managing Large Language Models (LLMs) locally, fitting 'Other Platforms' as it provides a user interface and endpoints for AI model handling, confirmed AI-related via AI/ML bug bounty context.
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly neutralizes the '\..\filename' sequence before pathname resolution occurs.
Access enforcement denies requests that resolve outside the intended directory even when the traversal sequence is present.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that block this traversal vector.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can discover path-traversal flaws but does not itself prevent them in production code.
Application security requirements can mandate input validation and path canonicalization to block traversal sequences.
Secure architecture principles include directory sandboxing and safe file-access design that mitigate path traversal.
Secure coding standards directly require neutralizing path traversal sequences such as '\..\filename'.