CVE-2024-2288: parisneo/lollms-webui · Cross-Site Request Forgery (CSRF)
Affects parisneo/lollms-webuiSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 9.3 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.3
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade parisneo/lollms-webui to 9.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubparisneo/lollms-webuipkg:github/parisneo/lollms-webuiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The primary mitigation is to upgrade parisneo/lollms-webui to version 9.3 or later, where the vulnerability is fixed. Until upgrade is possible, organizations should implement strict CSRF protections such as anti-CSRF tokens on all state-changing requests, especially the profile picture upload endpoint. Input validation and sanitization should be enforced to prevent malicious payloads in uploaded files. Web application firewalls (WAFs) can be configured to detect and block suspicious requests targeting the upload functionality. User education to avoid clicking on untrusted links can reduce risk of exploitation. Monitoring filesystem usage and upload patterns can help detect abuse attempts early. Additionally, applying Content Security Policy (CSP) headers can mitigate impact of stored XSS by restricting script execution contexts.
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in the profile picture upload functionality of the Lollms application, specifically in the parisneo/lollms-webui repository, affecting versions up to 7.3.0. This vulnerability allows attackers to change a victim's profile picture without their consent, potentially leading to a denial of service by overloading the filesystem with files. Additionally, this flaw can be exploited to perform a stored cross-site scripting (XSS) attack, enabling attackers to execute arbitrary JavaScript in the context of the victim's browser session. The issue is resolved in version 9.3.