# CVE-2024-5482: SSRF in add_webpage endpoint in parisneo/lollms-webui

> Attackers can exploit insufficient URL validation in the add_webpage endpoint to access internal resources or disrupt services via Server-Side Request Forgery.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-gfw7-f889-5p73

## What is CVE-2024-5482?

CVE-2024-5482 is a high-severity server-side request forgery vulnerability in parisneo/lollms-webui, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Server-Side Request Forgery (SSRF) vulnerability exists in the 'add_webpage' endpoint of the parisneo/lollms-webui application, affecting the latest version. The vulnerability arises because the application does not adequately validate URLs entered by users, allowing them to input arbitrary URLs, including those that target internal resources such as 'localhost' or '127.0.0.1'. This flaw enables attackers to make unauthorized requests to internal or external systems, potentially leading to access to sensitive data, service disruption, network integrity compromise, business logic manipulation, and abuse of third-party resources. The issue is critical and requires immediate attention to maintain the application's security and integrity.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Lollms Lollms Web Ui.

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

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

## Is CVE-2024-5482 being exploited?

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

## 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-5482 and fix it if it is affected.

What it is: CVE-2024-5482 is a high-severity server-side request forgery vulnerability in parisneo/lollms-webui, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, 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-5482 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-5482/ (Markdown: https://insights.sbomify.com/CVE-2024-5482/index.md)
```

## Sources

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

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