Profile alteration and stored XSS via CSRF
Published Jun 6, 2024 · Updated Oct 15, 2025
CSRF in ParisNeo LoLLMs WebUI before 9.3 allows remote attackers to replace a profile picture through a victim's browser. The profile-picture upload accepts a state-changing file submission without validating an anti-CSRF token and stores attacker-supplied content for later rendering. A victim must load attacker-controlled content while the WebUI is reachable; successful requests can consume filesystem space or execute stored JavaScript in the browser.
Summary
What happened
CSRF in ParisNeo LoLLMs WebUI before 9.3 allows remote attackers to replace a profile picture through a victim's browser. The profile-picture upload accepts a state-changing file submission without validating an anti-CSRF token and stores attacker-supplied content for later rendering. A victim must load attacker-controlled content while the WebUI is reachable; successful requests can consume filesystem space or execute stored JavaScript in the browser.
The record
- CVE
- CVE-2024-2288
- Published
- Jun 6, 2024
- Updated
- Oct 15, 2025
- Vendor
- ParisNeo
- Product
- LoLLMs WebUI
- Classifications
- CWE-352, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2024CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7.3.0
- Affected versionversion=unspecified <9.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Huntr profile-picture CSRF proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo