An unauthenticated SSRF vulnerability in lollms-webui poses a critical risk to cloud infrastructure by allowing attackers to exfiltrate sensitive IAM credentials and scan internal networks.

This vulnerability is a Server-Side Request Forgery (SSRF) residing in the @router.post("/api/proxy") endpoint. It allows an unauthenticated remote attacker to coerce the server into performing arbitrary GET requests against internal or external resources.

A successful exploit could lead to the total compromise of cloud-hosted environments through the exfiltration of AWS or GCP IAM metadata tokens. Furthermore, attackers can use the vulnerable instance as a pivot point to map and attack internal network services that are not exposed to the public internet. The CVSS score of 9.1 reflects the critical nature of this flaw and the high potential for unauthorized access to sensitive infrastructure.

Immediate Action: As no official patch is currently available, administrators should immediately disable public access to the lollms-webui interface or implement strict IP whitelisting.

Proactive Monitoring: Review web server access logs for unusual POST requests directed at the /api/proxy endpoint and monitor outbound traffic for connections to cloud metadata services (e.g., 169.254.169.254).

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules specifically designed to block requests containing internal IP addresses or metadata service URLs in the proxy payload.

Public Exploit Available: No

The severity of this SSRF vulnerability cannot be overstated, particularly for deployments in cloud environments. Organizations should consider the software "at-risk" until a formal patch is released. Immediate network-level isolation is the only effective way to mitigate the risk of credential theft and lateral movement at this time.