CVE-2024-6250: Lollms Web UI Path Traversal Vulnerability

CVE-2024-6250 Overview

CVE-2024-6250 is an absolute path traversal vulnerability [CWE-36] in parisneo/lollms-webui version 9.6. The flaw resides in the open_file endpoint defined in lollms_advanced.py. The endpoint invokes the sanitize_path function with allow_absolute_path=True, which permits attackers to supply absolute file paths that bypass path restrictions. Remote unauthenticated attackers can read arbitrary files and enumerate directories on affected Windows hosts. The issue affects confidentiality of the underlying operating system, including configuration files, credentials, and application data.

Critical Impact
Unauthenticated network attackers can read arbitrary files and list directories on Windows systems running lollms-webui v9.6.

Affected Products

lollms lollms_web_ui version 9.6
Deployments running the open_file endpoint in lollms_advanced.py
Windows-based installations of lollms-webui

Discovery Timeline

2024-06-27 - CVE-2024-6250 published to the National Vulnerability Database (NVD)
2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-6250

Vulnerability Analysis

The vulnerability affects the open_file endpoint inside lollms_advanced.py. The endpoint accepts a file path parameter from the client and passes it to the internal sanitize_path helper. The helper is invoked with the allow_absolute_path=True flag, which disables the standard normalization that would confine access to the application working directory.

Because the sanitizer intentionally permits absolute paths, an attacker can send fully qualified Windows paths such as drive-letter references or UNC-style paths. The application then reads or enumerates the target location and returns the content to the caller. No authentication, user interaction, or privileged position on the network is required.

EPSS scoring places this issue in the top quartile of vulnerabilities likely to see exploitation activity, reflecting the low complexity of the attack.

Root Cause

The root cause is insecure configuration of the path sanitization routine. Setting allow_absolute_path=True in the open_file route neutralizes the traversal protections that sanitize_path would otherwise apply. The function trusts client-supplied absolute paths, resulting in a classic [CWE-36] absolute path traversal condition.

Attack Vector

Exploitation occurs over the network against the HTTP interface exposed by lollms-webui. An attacker crafts a request to the open_file endpoint with an absolute path targeting sensitive files, such as configuration files, .env secrets, private keys, or Windows system files. The application responds with the requested file content or directory listing, disclosing information to the attacker.

The vulnerability does not require an existing session, and no exploit code is required in the wild — a single HTTP request suffices. See the Huntr Bounty Report for technical details.

Detection Methods for CVE-2024-6250

Indicators of Compromise

HTTP requests to the /open_file endpoint containing absolute paths such as C:\, D:\, or UNC prefixes like \\.
Requests referencing sensitive Windows locations such as C:\Windows\System32\config\, C:\Users\, or application secrets directories.
Sequential requests enumerating directory structures outside the lollms-webui installation directory.
Unusual outbound file read patterns from the lollms-webui process on Windows hosts.

Detection Strategies

Inspect web server and application logs for open_file requests containing drive-letter patterns or path characters outside the expected working directory.
Deploy web application firewall rules matching absolute path indicators in query parameters and JSON bodies to the open_file route.
Correlate lollms-webui process file-read telemetry with parent HTTP request identifiers to surface out-of-scope file access.

Monitoring Recommendations

Enable verbose access logging on the lollms-webui HTTP interface and forward events to a centralized log platform for retention and search.
Alert on file reads by the lollms-webui process targeting paths outside its installation and models directories.
Track authentication-free access to administrative endpoints and flag high-volume requests from single source IPs.

How to Mitigate CVE-2024-6250

Immediate Actions Required

Restrict network exposure of lollms-webui by binding the service to localhost or placing it behind an authenticated reverse proxy.
Block external access to the /open_file endpoint at the perimeter until a patched version is deployed.
Audit Windows hosts running v9.6 for evidence of unauthorized file reads or directory enumeration.
Rotate credentials, API keys, and tokens stored on affected systems that may have been exposed.

Patch Information

No vendor advisory URL is listed in the NVD record at time of writing. Users should upgrade to the latest release of parisneo/lollms-webui beyond version 9.6 and verify that the open_file endpoint no longer accepts absolute paths. Refer to the Huntr Bounty Report for remediation guidance from the researcher.

Workarounds

Modify lollms_advanced.py to call sanitize_path with allow_absolute_path=False and validate that resolved paths remain within an allowlisted base directory.
Run lollms-webui under a low-privilege Windows service account with read access limited to required directories.
Deploy WAF or reverse proxy rules that reject requests to /open_file containing :, \, or path traversal sequences.
Isolate lollms-webui deployments on segmented networks with no direct internet exposure until patched.

bash

# Configuration example: reverse proxy rule blocking absolute paths to open_file
location /open_file {
    if ($args ~* "([a-zA-Z]:[\\/]|\.\.[\\/]|%5C|%2E%2E)") {
        return 403;
    }
    proxy_pass http://127.0.0.1:9600;
}