# CVE-2024-10906: Cross-Site Request Forgery (CSRF) in eosphoros-ai/db-gpt

> An attacker can perform Cross-Site Request Forgery attacks against DB-GPT server endpoints due to overly permissive CORS settings.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L`)
- **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-3248-f932-c76p, PYSEC-2026-1289

## What is CVE-2024-10906?

CVE-2024-10906 is a high-severity vulnerability in eosphoros-ai/db-gpt, 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

In version 0.6.0 of eosphoros-ai/db-gpt, the `uvicorn` app created by `dbgpt_server` uses an overly permissive instance of `CORSMiddleware` which sets the `Access-Control-Allow-Origin` to `*` for all requests. This configuration makes all endpoints exposed by the server vulnerable to Cross-Site Request Forgery (CSRF). An attacker can exploit this vulnerability to interact with any endpoints of the instance, even if the instance is not publicly exposed to the network.

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

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

3 open source packages ship an affected version, including dbgpt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |

Products: Dbgpt Db-Gpt.

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

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

## Is CVE-2024-10906 being exploited?

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

## Other vulnerabilities in eosphoros-ai/db-gpt

- [CVE-2024-10831](https://insights.sbomify.com/CVE-2024-10831/): Arbitrary File Write through Absolute Path Traversal in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10833](https://insights.sbomify.com/CVE-2024-10833/): Arbitrary File Write in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10834](https://insights.sbomify.com/CVE-2024-10834/): Arbitrary File Write in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10835](https://insights.sbomify.com/CVE-2024-10835/): Arbitrary File Write via SQL Injection in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10901](https://insights.sbomify.com/CVE-2024-10901/): Arbitrary File Write via DuckDB SQL Injection in eosphoros-ai/db-gpt (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10906 is a high-severity vulnerability in eosphoros-ai/db-gpt, 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-10906 exists.

Affected packages and fixed versions:
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed

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

## Sources

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

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