# CVE-2024-3126: Command Injection in parisneo/lollms-webui

> Attackers can execute arbitrary commands remotely by manipulating the xtts_base_url parameter in the Lollms Web UI application.

- **Severity:** High 8.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6w8c-vq68-25hc

## What is CVE-2024-3126?

CVE-2024-3126 is a high-severity command injection vulnerability in parisneo/lollms-webui, published on 16 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A command injection vulnerability exists in the 'run_xtts_api_server' function of the parisneo/lollms-webui application, specifically within the 'lollms_xtts.py' script. The vulnerability arises due to the improper neutralization of special elements used in an OS command. The affected function utilizes 'subprocess.Popen' to execute a command constructed with a Python f-string, without adequately sanitizing the 'xtts_base_url' input. This flaw allows attackers to execute arbitrary commands remotely by manipulating the 'xtts_base_url' parameter. The vulnerability affects versions up to and including the latest version before 9.5. Successful exploitation could lead to arbitrary remote code execution (RCE) on the system where the application is deployed.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Lollms Lollms Web Ui.

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

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

## Is CVE-2024-3126 being exploited?

There is no known exploitation of CVE-2024-3126 in the wild and no public exploit code.

## Other vulnerabilities in parisneo/lollms-webui

- [CVE-2024-2359](https://insights.sbomify.com/CVE-2024-2359/): Improper Neutralization of Special Elements used in an OS Command in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-2360](https://insights.sbomify.com/CVE-2024-2360/): Path Traversal leading to Remote Code Execution in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-4320](https://insights.sbomify.com/CVE-2024-4320/): Remote Code Execution due to LFI in '/install_extension' in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-2358](https://insights.sbomify.com/CVE-2024-2358/): Path Traversal leading to Remote Code Execution in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-4326](https://insights.sbomify.com/CVE-2024-4326/): Remote Code Execution via `/apply_settings` and `/execute_code` in parisneo/lollms-webui (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3126 is a high-severity command injection vulnerability in parisneo/lollms-webui, published on 16 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3126 in the wild and no public exploit code.

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-3126/ (Markdown: https://insights.sbomify.com/CVE-2024-3126/index.md)
```

## Sources

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

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