# CVE-2024-4839: CSRF in Servers Configurations in parisneo/lollms-webui

> Attackers can trick users into installing unauthorized services via CSRF in the Servers Configurations function of lollms-webui.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-v2f9-5493-gg7h

## What is CVE-2024-4839?

CVE-2024-4839 is a medium-severity vulnerability in parisneo/lollms-webui, published on 24 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability exists in the 'Servers Configurations' function of the parisneo/lollms-webui, versions 9.6 to the latest. The affected functions include Elastic search Service (under construction), XTTS service, Petals service, vLLM service, and Motion Ctrl service, which lack CSRF protection. This vulnerability allows attackers to deceive users into unwittingly installing the XTTS service among other packages by submitting a malicious installation request. Successful exploitation results in attackers tricking users into performing actions without their consent.

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

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

It affects 1 product.


Products: Lollms Lollms-Webui.

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

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

## Is CVE-2024-4839 being exploited?

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

## Other vulnerabilities in parisneo/lollms-webui

- [CVE-2024-4267](https://insights.sbomify.com/CVE-2024-4267/): Remote Code Execution in parisneo/lollms-webui (high 8.4)
- [CVE-2024-1646](https://insights.sbomify.com/CVE-2024-1646/): Authentication Bypass in parisneo/lollms-webui (high 8.2)
- [CVE-2024-1601](https://insights.sbomify.com/CVE-2024-1601/): SQL Injection in parisneo/lollms-webui (high 7.5)
- [CVE-2024-5125](https://insights.sbomify.com/CVE-2024-5125/): XSS and Open Redirect via SVG File Upload in parisneo/lollms-webui (high 7.3)
- [CVE-2024-1569](https://insights.sbomify.com/CVE-2024-1569/): Uncontrolled Resource Consumption in parisneo/lollms-webui (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4839 is a medium-severity vulnerability in parisneo/lollms-webui, published on 24 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4839 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-4839/ (Markdown: https://insights.sbomify.com/CVE-2024-4839/index.md)
```

## Sources

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

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