How broadly exploitable is this SSRF vulnerability?

Exploitability is broad whenever the LoLLMs WEBUI instance is reachable over the network, especially if the `/api/proxy` endpoint is exposed to the internet. Because the vulnerable route is unauthenticated, any external user who can send HTTP requests to the service can attempt SSRF.

Does an attacker need valid credentials or an existing account to exploit this issue?

No. The described behavior indicates that the proxy endpoint lacks authentication, so exploitation generally does not require credentials or a registered account. Network access to the WEBUI host and knowledge of the `/api/proxy` path are sufficient.

What is the safest general fix pattern for this kind of vulnerability?

The safest pattern is to either remove generic proxy functionality entirely or implement a tightly controlled fetch mechanism that is authenticated, authorized, and restricted to a small, explicit allowlist of destinations. In addition, enforce IP and scheme restrictions and block access to internal and metadata address ranges.

Severity:

CRITICAL RISK

(9.1)

Unauthenticated SSRF (CWE-918) in LoLLMs WEBUI Proxy Endpoint

CVE-2026-33340

Published:

Mar 24, 2026

Status:

Awaiting Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-306;CWE-918

Impact:

Network pivoting and sensitive data exposure via server-initiated requests

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-306;CWE-918

Impact:

Network pivoting and sensitive data exposure via server-initiated requests

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Unauthenticated SSRF (CWE-918) in LoLLMs WEBUI Proxy Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare