# CVE-2024-38514: NextChat Server-Side Request Forgery (SSRF)

> Attackers can exploit SSRF in NextChat to perform arbitrary requests or execute JavaScript in users' browsers via the WebDav API.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-gph5-rx77-3pjg

## What is CVE-2024-38514?

CVE-2024-38514 is a high-severity server-side request forgery vulnerability in ChatGPTNextWeb ChatGPT-Next-Web, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NextChat is a cross-platform ChatGPT/Gemini UI. There is a Server-Side Request Forgery (SSRF) vulnerability due to a lack of validation of the `endpoint` GET parameter on the WebDav API endpoint. This SSRF can be used to perform arbitrary HTTPS request from the vulnerable instance (MKCOL, PUT and GET methods supported), or to target NextChat users and make them execute arbitrary JavaScript code in their browser. This vulnerability has been patched in version 2.12.4.

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

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


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

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

## Is CVE-2024-38514 being exploited?

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

Public exploit code:

- NextChat - Server-Side Request Forgery (nuclei): http/cves/2024/CVE-2024-38514.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38514 is a high-severity server-side request forgery vulnerability in ChatGPTNextWeb ChatGPT-Next-Web, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38514 exists.

Affected product: ChatGPTNextWeb ChatGPT-Next-Web. 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-38514/ (Markdown: https://insights.sbomify.com/CVE-2024-38514/index.md)
```

## Sources

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

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