SSRF in parisneo/lollms-webui

The SSRF vulnerability in lollms-webui allows an attacker to craft malicious requests through the /api/proxy endpoint. By manipulating the url parameter within a POST request (e.g., {"url":"http://steal.target"}), an attacker can force the server to make requests to arbitrary internal or external URLs. This can lead to the exposure of sensitive data, unauthorized access to internal services, and potentially even the execution of malicious code on systems accessible from the lollms-webui server. The impact is amplified if the server has access to privileged credentials or is part of a larger, interconnected network, enabling lateral movement and a wider blast radius.

Organizations deploying lollms-webui, particularly those exposing it to untrusted networks or using it to proxy requests to internal services, are at risk. Shared hosting environments where multiple users share the same server instance are also vulnerable, as an attacker could potentially exploit the vulnerability through another user's account.

• python / server:

import requests
import json

url = 'http://your_lollms_webui_ip/api/proxy'
headers = {'Content-Type': 'application/json'}
data = json.dumps({'url': 'http://127.0.0.1:8080'}) # Test URL

response = requests.post(url, headers=headers, data=data)

if response.status_code == 200:
    print("Potential SSRF detected.  Review response content.")
    print(response.text)
else:
    print("Request failed.")

• generic web:

curl -v -X POST 'http://your_lollms_webui_ip/api/proxy' -H 'Content-Type: application/json' -d '{"url":"http://127.0.0.1:8080"}'

• linux / server:

journalctl -u lollms-webui -f | grep "proxy request" # Look for suspicious URLs in logs

1. 2025-03-20Disclosure

   disclosure

1. Reserviert2024-12-18
2. Veröffentlicht2025-03-20
3. EPSS aktualisiert2026-04-02

While a direct patch for CVE-2024-12766 is pending, several mitigation strategies can reduce the risk. The most effective is to restrict outbound network access from the lollms-webui server, limiting its ability to make requests to external resources. Implement strict URL validation on the /api/proxy endpoint, rejecting requests with invalid or suspicious URLs. Consider using a Web Application Firewall (WAF) to filter malicious requests and block SSRF attempts. Regularly review and update the server's configuration, ensuring that security mechanisms like forbidremoteaccess and check_access are properly configured and enforced. After implementing these workarounds, verify their effectiveness by attempting to trigger the SSRF vulnerability with a controlled, non-harmful URL.