# CVE-2024-4328: CSRF in clear_personality_files_list in parisneo/lollms-webui

> Attackers can trick users into deleting personality files via CSRF in lollms-webui, requiring a patch to prevent unauthorized data modification.

- **Severity:** Medium 4.0 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-mf32-4qcq-96wh

## What is CVE-2024-4328?

CVE-2024-4328 is a medium-severity vulnerability in parisneo/lollms-webui, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability exists in the clear_personality_files_list function of the parisneo/lollms-webui v9.6. The vulnerability arises from the use of a GET request to clear personality files list, which lacks proper CSRF protection. This flaw allows attackers to trick users into performing actions without their consent, such as deleting important files on the system. The issue is present in the application's handling of requests, making it susceptible to CSRF attacks that could lead to unauthorized actions being performed on behalf of the user.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-4328?

It affects 1 product.


Products: Parisneo Lollms Web Ui.

## How do I fix CVE-2024-4328?

No fix has been published for CVE-2024-4328 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-4328 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4328 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4328 and fix it if it is affected.

What it is: CVE-2024-4328 is a medium-severity vulnerability in parisneo/lollms-webui, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4328 exists.

Affected product: parisneo/lollms-webui. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4328/ (Markdown: https://insights.sbomify.com/CVE-2024-4328/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4328
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4328
- OSV: https://osv.dev/vulnerability/CVE-2024-4328

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4328/
Summaries are generated and may contain mistakes; the official description above is the record.