Cyber Resilience

CVE-2024-2356

Published
02 February 2026
Modified
15 April 2026
CVSS Score v3 9.6
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0077 52th percentile
Risk Priority 69 floored blend · peak EPSS

Summary

CVE-2024-2356 is a critical-severity Path Traversal: '\..\filename' (CWE-29) vulnerability. Its CVSS base score is 9.6 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

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.

EU & UK References

Vulnerability Data

A Local File Inclusion (LFI) vulnerability exists in the '/reinstall_extension' endpoint of the parisneo/lollms-webui application, specifically within the `name` parameter of the `@router.post("/reinstall_extension")` route. This vulnerability allows attackers to inject a malicious `name` parameter, leading to the server loading and…

more

executing arbitrary Python files from the upload directory for discussions. This issue arises due to the concatenation of `data.name` directly with `lollmsElfServer.lollms_paths.extensions_zoo_path` and its use as an argument for `ExtensionBuilder().build_extension()`. The server's handling of the `__init__.py` file in arbitrary locations, facilitated by `importlib.machinery.SourceFileLoader`, enables the execution of arbitrary code, such as command execution or creating a reverse-shell connection. This vulnerability affects the latest version of parisneo/lollms-webui and can lead to Remote Code Execution (RCE) when the application is exposed to an external endpoint or the UI, especially when bound to `0.0.0.0` or in `headless mode`. No user interaction is required for exploitation.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-6130Shared CWE-29
CVE-2024-12389Shared CWE-29
CVE-2025-58291Shared CWE-29
CVE-2025-50184Shared CWE-29
CVE-2024-8537Shared CWE-29
CVE-2025-66608Shared CWE-29
CVE-2024-2178Shared CWE-29
CVE-2023-1034Shared CWE-29
CVE-2023-6977Shared CWE-29
CVE-2023-2780Shared CWE-29

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.

PR.PS-06 mostly match
prevents

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.

finds

Security testing can discover path-traversal flaws but does not itself prevent them in production code.

prevents

Application security requirements can mandate input validation and path canonicalization to block traversal sequences.

prevents

Secure architecture principles include directory sandboxing and safe file-access design that mitigate path traversal.

prevents

Secure coding standards directly require neutralizing path traversal sequences such as '\..\filename'.

References