Skip to main content
CVE Vulnerability Database

CVE-2024-9919: Lollms Web UI Authentication Bypass Vulnerability

CVE-2024-9919 is an authentication bypass flaw in Lollms Web UI V13 that enables unauthorized directory deletions through a missing authentication check. This post covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

CVE-2024-9919 Overview

CVE-2024-9919 is a missing authentication vulnerability in the parisneo/lollms-webui V13 application. The /uninstall/{app_name} API endpoint fails to invoke the check_access() function that validates the client_id. An attacker with local access can call this endpoint without credentials and trigger unauthorized directory deletions on the host. The flaw is classified under [CWE-306] Missing Authentication for Critical Function. It affects the integrity and availability of the application and any data stored within reachable directory paths.

Critical Impact

Unauthenticated invocation of the uninstall endpoint permits arbitrary directory deletion, resulting in data loss and disruption of the lollms-webui service.

Affected Products

  • parisneo/lollms-webui version 13
  • Deployments exposing the lollms-webui HTTP API locally
  • Environments where the uninstall route is reachable by non-administrative users

Discovery Timeline

  • 2025-03-20 - CVE-2024-9919 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-9919

Vulnerability Analysis

The vulnerability resides in the application uninstall handler exposed at /uninstall/{app_name}. The route accepts an application name as a path parameter and proceeds to remove the associated directory from disk. Other privileged endpoints in lollms-webui invoke check_access() to validate the caller's client_id before performing destructive actions. The uninstall route omits this check entirely.

Because authorization enforcement is absent, any process able to reach the API can trigger a directory removal operation. The impact extends beyond the intended plugin or extension directory when app_name is influenced to resolve outside the expected base path.

Root Cause

The root cause is a missing authentication call [CWE-306] in the request handler. The developer did not wire the shared access-control routine into the uninstall path. Access control is applied inconsistently across route handlers, leaving this endpoint effectively public within its network scope.

Attack Vector

Exploitation requires local network reachability to the lollms-webui HTTP service. An attacker sends an HTTP request to /uninstall/{app_name} with an attacker-chosen application name. The server responds by deleting the corresponding directory without verifying identity or authorization. See the Huntr Bug Bounty Report for technical details.

No public proof-of-concept exploit code is listed for this CVE. The vulnerability mechanism is described in prose per the referenced advisory.

Detection Methods for CVE-2024-9919

Indicators of Compromise

  • Unexpected HTTP POST or DELETE requests to /uninstall/{app_name} in lollms-webui access logs
  • Missing directories under the lollms-webui personalities, extensions, or applications folders
  • Requests to the uninstall route lacking a valid session or client_id header
  • Sudden functional degradation or missing installed apps in the lollms-webui interface

Detection Strategies

  • Inspect application logs for calls to /uninstall/ and correlate with authenticated session identifiers
  • Enable file system audit logging on lollms-webui data directories to capture deletion events with parent process context
  • Alert on HTTP request patterns targeting the uninstall route from unexpected source addresses

Monitoring Recommendations

  • Forward lollms-webui HTTP logs and host file system audit events to a central logging platform
  • Baseline normal administrative activity on the uninstall endpoint and alert on deviations
  • Monitor for repeated 200-status responses to uninstall calls that do not correlate with an operator session

How to Mitigate CVE-2024-9919

Immediate Actions Required

  • Restrict network exposure of the lollms-webui service to trusted local users only
  • Place the application behind an authenticating reverse proxy that enforces access control on /uninstall/*
  • Audit installed application directories and back up critical data before further use
  • Review the Huntr Bug Bounty Report for current remediation status

Patch Information

No vendor patch link is listed in the NVD record at the time of publication. Track the upstream parisneo/lollms-webui repository for a fix that adds check_access() enforcement to the /uninstall/{app_name} handler. Upgrade to any version later than V13 that includes the authentication check once released.

Workarounds

  • Bind the lollms-webui listener to 127.0.0.1 and require SSH tunneling for remote administration
  • Add a reverse proxy rule that denies access to /uninstall/ from all clients except authorized administrators
  • Run lollms-webui under a dedicated low-privilege user with directory permissions limited to its own data paths
  • Disable or remove the uninstall route in local forks until an official fix is available
bash
# Configuration example: nginx rule to block unauthenticated access to the uninstall endpoint
location ~ ^/uninstall/ {
    allow 127.0.0.1;
    deny all;
    auth_basic "lollms admin";
    auth_basic_user_file /etc/nginx/.htpasswd;
    proxy_pass http://127.0.0.1:9600;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.