Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-2624 is a critical-severity Path Traversal: '\..\filename' (CWE-29) vulnerability in Lollms Lollms Web Ui. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique File and Directory Discovery (T1083); ranked in the top 31% of CVEs by exploit likelihood; 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; MITRE ATLAS techniques in scope: Obtain Capabilities (AML.T0016), Exfiltration via AI Inference API (AML.T0024), LLM Prompt Injection (AML.T0051).
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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.
CVE-2024-2624 is a path traversal and arbitrary file upload vulnerability in the parisneo/lollms-webui application. It resides in the /switch_personal_path endpoint within lollms_core/lollms/server/endpoints/lollms_user.py, where the path parameter receives insufficient sanitization. The flaw permits attackers to reference arbitrary filesystem locations, enabling direct file uploads, disclosure of personal_data contents, and overwriting of configuration files stored under the same-named directory. The issue affects the latest release prior to the fix and carries a CVSS 3.1 score of 9.8.
An unauthenticated remote attacker can invoke the endpoint with a crafted path value to upload malicious files, exfiltrate sensitive user data, or replace critical configuration entries. Successful exploitation can lead to sensitive information disclosure, unauthorized file placement, and remote code execution through configuration tampering.
The vulnerability was addressed in version 9.4. Public references point to a specific commit (aeba79f3ea934331b8ecd625a58bae6e4f7e7d3f) that implements the correction, along with a detailed report on huntr.com.
EPSS for the CVE rose from lower values to a recorded peak of 0.1033 on 2026-03-16 before receding to the current 0.0631, indicating a measurable increase in exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-27573
Vulnerability Data
A path traversal and arbitrary file upload vulnerability exists in the parisneo/lollms-webui application, specifically within the `@router.get("/switch_personal_path")` endpoint in `./lollms-webui/lollms_core/lollms/server/endpoints/lollms_user.py`. The vulnerability arises due to insufficient sanitization of user-supplied input for the `path` parameter, allowing an attacker to specify arbitrary…
more
file system paths. This flaw enables direct arbitrary file uploads, leakage of `personal_data`, and overwriting of configurations in `lollms-webui`->`configs` by exploiting the same named directory in `personal_data`. The issue affects the latest version of the application and is fixed in version 9.4. Successful exploitation could lead to sensitive information disclosure, unauthorized file uploads, and potentially remote code execution by overwriting critical configuration files.
- 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
- The vulnerability affects parisneo/lollms-webui, a web-based user interface platform for managing and interacting with large language models (LLMs), categorized as Other Platforms.
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Path traversal enables arbitrary file reads (T1083: File and Directory Discovery). Arbitrary file uploads facilitate tool/file transfer into the environment (T1105: Ingress Tool Transfer). Vulnerability in public-facing web endpoint allows exploitation (T1190: Exploit Public-Facing Application).
MITRE ATLAS TechniquesAI
MITRE ATLAS techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation and sanitization of the user-supplied path parameter to block traversal sequences and arbitrary filesystem references.
Enforces access-control policy on the /switch_personal_path endpoint so that only authorized subjects may perform file operations within allowed directories.
Restricts the ability to modify or overwrite configuration files under personal_data or configs directories to authorized change processes only.
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.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
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'.
Information access restriction limits which files an application may read or write.