CVE-2024-10835: DB-GPT is vulnerable to SQL Injection attacks from unauthenticated users

CVE-2024-10835 · Severity: critical · CVSS 9.1 · Published 2025-03-20

In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /api/v1/editor/sql/run` allows execution of arbitrary SQL queries without any access control. This vulnerability can be exploited by attackers to perform Arbitrary File Write using DuckDB SQL, enabling them to write arbitrary files to the victim's file system. This can potentially lead to Remote Code Execution (RCE).

Technologies: dbgpt (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-10835 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-10835 being exploited in the wild.
How severe is CVE-2024-10835?
Critical severity, with a CVSS score of 9.1, published 20 March 2025.
Which products and versions are affected?
dbgpt (PyPI) < 0.7.1, ECOSYSTEM:introduced=0,fixed=0.7.1.
Is there a fix for CVE-2024-10835?
Yes. dbgpt (PyPI): upgrade to 0.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-10835?
Check whether you run dbgpt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • dbgpt (PyPI): upgrade to 0.7.1 or later
    pip install "dbgpt>=0.7.1"

Affected products

  • dbgpt (PyPI) < 0.7.1, ECOSYSTEM:introduced=0,fixed=0.7.1

Identifiers

  • CVE-2024-10835
  • GHSA-qccg-9m4q-xfm6
  • PYSEC-2026-325

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.