Security Resilience

CVE-2024-2366

RCE in Lollms Web Ui ≤ 9.5

Published
16 May 2024
Modified
09 July 2025
Patch / advisory
CVSS Score v3 9.0
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0066 51th percentile
Risk Priority 68 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-2366 is a critical-severity Command Injection (CWE-77) vulnerability in Lollms Lollms Web Ui. Its CVSS base score is 9.0 (Critical).

Operationally, ranked in the top 49% 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 Other ATLAS/OWASP Terms risk domain.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A remote code execution vulnerability exists in the parisneo/lollms-webui application, specifically within the reinstall_binding functionality in lollms_core/lollms/server/endpoints/lollms_binding_infos.py of the latest version. The vulnerability arises due to insufficient path sanitization, allowing an attacker to exploit path traversal to navigate to arbitrary…

more

directories. By manipulating the binding_path to point to a controlled directory and uploading a malicious __init__.py file, an attacker can execute arbitrary code on the server.

CWE(s)

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
Other ATLAS/OWASP Terms
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
The vulnerability is in parisneo/lollms-webui, a web UI platform for running and managing large language models (LOLLMS), which qualifies as an AI/ML platform. The issue occurs in binding management endpoints, fitting 'Other Platforms' as a catch-all for AI web interfaces and deployment tools.

Related Threats

CVEs Like This One

CVE-2024-4322Same product: Lollms Lollms Web Ui
CVE-2024-6673Same product: Lollms Lollms Web Ui
CVE-2024-6040Same product: Lollms Lollms Web Ui
CVE-2024-4897Same product: Lollms Lollms Web Ui
CVE-2024-2548Same product: Lollms Lollms Web Ui
CVE-2024-1522Same product: Lollms Lollms Web Ui
CVE-2024-2358Same product: Lollms Lollms Web Ui
CVE-2024-2361Same product: Lollms Lollms Web Ui
CVE-2024-2360Same product: Lollms Lollms Web Ui
CVE-2024-1511Same product: Lollms Lollms Web Ui

Affected Assets

lollms
lollms web ui
≤ 9.5

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Secure engineering principles include proper neutralization and safe command construction practices.

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.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References