CVE-2024-2356: Lollms-WebUI LFI to RCE Vulnerability

CVE-2024-2356 Overview

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 executing arbitrary Python files from the upload directory for discussions. The vulnerability can escalate to Remote Code Execution (RCE) when the application is exposed to an external endpoint or when bound to 0.0.0.0 or running in headless mode.

Critical Impact

This vulnerability enables attackers to achieve Remote Code Execution without user interaction, potentially allowing command execution or reverse-shell connections on affected systems.

Affected Products

• parisneo/lollms-webui (latest version at time of disclosure)
• Deployments exposed externally or bound to 0.0.0.0
• Instances running in headless mode

Discovery Timeline

• 2026-02-02 - CVE CVE-2024-2356 published to NVD
• 2026-02-03 - Last updated in NVD database

Technical Details for CVE-2024-2356

Vulnerability Analysis

This vulnerability arises from improper input validation in the /reinstall_extension endpoint. The issue stems from direct concatenation of user-supplied input (data.name) with the lollmsElfServer.lollms_paths.extensions_zoo_path, which is then passed as an argument to ExtensionBuilder().build_extension(). The server's use of importlib.machinery.SourceFileLoader to handle the __init__.py file in arbitrary locations enables execution of malicious Python code.

The vulnerability is classified under CWE-29 (Path Traversal: '..\filename'), indicating that path manipulation through specially crafted input allows attackers to traverse directories and access files outside the intended scope. When combined with Python's dynamic module loading capabilities, this creates a direct path to arbitrary code execution.

Root Cause

The root cause is the lack of proper path sanitization for the name parameter in the extension reinstallation endpoint. The application directly concatenates user input with internal file paths without validating or sanitizing the input for path traversal sequences. This allows attackers to manipulate the path to point to arbitrary locations within the file system where they may have previously uploaded malicious Python files through the discussions upload functionality.

Attack Vector

The attack is network-based and requires no user interaction for exploitation. An attacker can craft a malicious POST request to the /reinstall_extension endpoint with a manipulated name parameter containing path traversal sequences. This causes the server to load a malicious __init__.py file from an attacker-controlled location, resulting in arbitrary code execution with the privileges of the web application.

The attack flow involves:

1. Uploading a malicious Python file to the discussions upload directory
2. Sending a crafted request to /reinstall_extension with a path traversal payload
3. The server loads and executes the malicious __init__.py via SourceFileLoader
4. Arbitrary code execution achieved, enabling reverse shells or command execution

# Security patch in endpoints/chat_bar.py - Import additions for path sanitization
# Source: https://github.com/parisneo/lollms-webui/commit/41dbb1b3f2e78ea276e5269544e50514252c0c25

 import shutil
 import os
 import platform
+from urllib.parse import urlparse
 from functools import partial
 from datetime import datetime
 from utilities.execution_engines.python_execution_engine import execute_python
 from utilities.execution_engines.latex_execution_engine import execute_latex
 from utilities.execution_engines.shell_execution_engine import execute_bash
-
+from lollms.security import sanitize_path, forbid_remote_access
 from lollms.internet import scrape_and_save
+from urllib.parse import urlparse
 import threading
 # ----------------------- Defining router and main class ------------------------------

Detection Methods for CVE-2024-2356

Indicators of Compromise

• Unusual POST requests to /reinstall_extension endpoint containing path traversal sequences (../, ..\)
• Unexpected Python files appearing in the discussions upload directory
• Anomalous process spawning from the lollms-webui application process
• Outbound connections from the web server to suspicious external hosts (potential reverse shell activity)

Detection Strategies

• Monitor web application logs for requests to /reinstall_extension with suspicious name parameters containing directory traversal patterns
• Implement file integrity monitoring on the extensions directory and upload directories to detect unauthorized file additions
• Deploy network-based intrusion detection rules to identify path traversal attempts in HTTP POST body parameters
• Monitor for unusual child processes spawned by the Python web application

Monitoring Recommendations

• Enable verbose logging for the lollms-webui application to capture all API endpoint access
• Implement real-time alerting for any requests containing path traversal sequences
• Monitor system calls from the web application process for suspicious execution patterns
• Track file system changes in application directories for unauthorized modifications

How to Mitigate CVE-2024-2356

Immediate Actions Required

• Update lollms-webui to the patched version containing commit 41dbb1b3f2e78ea276e5269544e50514252c0c25
• Restrict network access to the application, avoiding binding to 0.0.0.0 unless absolutely necessary
• Implement network-level access controls to limit who can reach the web interface
• Review and remove any suspicious files from the discussions upload directory

Patch Information

The vulnerability has been addressed in a security patch committed to the lollms-webui repository. The fix introduces proper path sanitization using the sanitize_path function from lollms.security module, along with the forbid_remote_access function to prevent unauthorized remote exploitation.

# Security patch in endpoints/lollms_advanced.py - Improved path validation
# Source: https://github.com/parisneo/lollms-webui/commit/41dbb1b3f2e78ea276e5269544e50514252c0c25

 import subprocess   
 from typing import Optional
 
-# Regular expression pattern to validate file paths
-FILE_PATH_REGEX = r'^[a-zA-Z0-9_\-\\\\/]+$'
+from lollms.security import sanitize_path
 
-# Function to validate file paths using the regex pattern
 def validate_file_path(path):
-    return re.match(FILE_PATH_REGEX, path)
+    try:
+        sanitized_path = sanitize_path(path, allow_absolute_path=False)
+        return sanitized_path is not None
+    except Exception as e:
+        print(f"Path validation error: {str(e)}")
+        return False
 
 from utilities.execution_engines.python_execution_engine import execute_python
 from utilities.execution_engines.latex_execution_engine import execute_latex

Workarounds

• Do not expose the lollms-webui application to untrusted networks or the public internet
• Configure the application to bind only to localhost (127.0.0.1) if remote access is not required
• Implement a reverse proxy with strict input filtering to block path traversal patterns
• Disable headless mode if it is not required for your deployment

# Configuration example - Restrict binding to localhost only
# In your lollms-webui configuration or startup script:
export LOLLMS_HOST="127.0.0.1"
export LOLLMS_PORT="9600"

# If using a reverse proxy (nginx example):
# Add input validation to block path traversal attempts
location /reinstall_extension {
    if ($request_body ~* "\.\.") {
        return 403;
    }
    proxy_pass http://127.0.0.1:9600;
}