# CVE-2024-7819: CORS Misconfiguration in danswer-ai/danswer

> Attackers can steal sensitive data like API keys and chat contents via a CORS misconfiguration in the Danswer AI application.

- **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:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-2c36-wq4v-5v3h

## What is CVE-2024-7819?

CVE-2024-7819 is a high-severity vulnerability in danswer-ai/danswer, published on 20 Mar 2025. 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 CORS misconfiguration in danswer-ai/danswer v1.4.1 allows attackers to steal sensitive information such as chat contents, API keys, and other data. This vulnerability occurs due to improper validation of the origin header, enabling malicious web pages to make unauthorized requests to the application's API.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2024-7819 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7819 is a high-severity vulnerability in danswer-ai/danswer, published on 20 Mar 2025. 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-7819 exists.

Affected product: danswer-ai/danswer. 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-7819/ (Markdown: https://insights.sbomify.com/CVE-2024-7819/index.md)
```

## Sources

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

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