CVE-2024-4328 is a High (CVSS 8.1) cross site request forgery in lollms-webui 9.6. The clear_personality_files_list function runs on a GET request with no CSRF protection, so a web page can make a visitor's browser trigger file deletion. No fixed version is on record. Update to the latest release.
What's affected
- Product: parisneo lollms-webui, version 9.6.
- Affected function: clear_personality_files_list.
- Fixed version: none named in the record, whose only reference is a huntr report I did not fetch.
- Severity: High, CVSS 8.1. The vector needs user interaction (UI:R) and affects integrity and availability, not confidentiality.
- Exploitation: KEV is false.
- Sibling records: CVE-2024-4403 is another CSRF in the same app's restart_program function.
How to check if you're exposed
Find lollms-webui 9.6 installs. The practical question is whether the user who runs it also browses the web on the same machine, because CSRF works through the victim's own browser.
Check the personality files folder for files that disappeared without explanation. There is no good log for CSRF, so loss of data is often how it shows up.
What to do now
- Update lollms-webui beyond 9.6 and read the release notes.
- Avoid opening unknown links or sites in the same browser session while the app is running.
- Keep backups of personality files and other data the app manages.
- Bind the service to localhost and consider a reverse proxy that requires a token.
- Ask the maintainers to move state changing actions to POST with tokens if the latest version still uses GET.
Why it matters
The record maps this to CWE-352, cross site request forgery. A browser sends cookies and local network requests automatically, so any page can ask it to call another address. A state changing action on a GET route needs no form at all. An image tag can trigger it.
The repair has two parts. Actions that change state should use POST or DELETE, and the server should check a token the attacker cannot guess.
Quick check
Why is a GET request a problem?
Browsers load GET addresses freely, for example when a page includes an image. An action on GET can be triggered without the user doing anything on purpose.
Is localhost enough protection?
Not by itself. The victim's browser can still reach localhost, which is how CSRF against local tools works.
Scan your own dependencies
Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan checks a manifest against known advisories, and the Gold directory keeps this record's details in one place.
Sources
The NVD record for CVE-2024-4328 (published 2024-06-10) supplied the description, score and weakness data. Pages marked fetched were read for this post. The others are listed in the record and were not read.
Last reviewed: 19 October 2026.
