Cyber Resilience

CVE-2024-6959

CSRF in Lollms Web Ui 9.8

Public PoCCSRF
Published
13 October 2024
Modified
03 November 2024
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
EPSS Score 0.0021 11th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2024-6959 is a high-severity CSRF (CWE-352) vulnerability in Lollms Lollms Web Ui. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as LLM Application Platforms; in the Other ATLAS/OWASP Terms risk domain.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability in parisneo/lollms-webui version 9.8 allows for a Denial of Service (DOS) attack when uploading an audio file. If an attacker appends a large number of characters to the end of a multipart boundary, the system will continuously process…

more

each character, rendering lollms-webui inaccessible. This issue is exacerbated by the lack of Cross-Site Request Forgery (CSRF) protection, enabling remote exploitation. The vulnerability leads to service disruption, resource exhaustion, and extended downtime.

CWE(s)

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
Other ATLAS/OWASP Terms
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
lollms-webui is an open-source web user interface for running, managing, and interacting with large language models (LLMs) and multimodal AI systems locally, fitting as an other AI platform.

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-2288Same product: Lollms Lollms Web Ui
CVE-2024-6673Same product: Lollms Lollms Web Ui
CVE-2024-6040Same product: Lollms Lollms Web Ui
CVE-2024-1522Same product: Lollms Lollms Web Ui
CVE-2024-8736Same product: Lollms Lollms Web Ui
CVE-2024-4403Same vendor: Lollms
CVE-2024-4839Same vendor: Lollms
CVE-2024-4499Same vendor: Lollms
CVE-2025-47470Shared CWE-352
CVE-2024-5616Shared CWE-352

Affected Assets

lollms
lollms web ui
9.8

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References