Skip to main content

Db Gpt CVE-2026-4504

| EUVDEUVD-2026-13804 MEDIUM
SQL Injection (CWE-89)
2026-03-20 VulDB
5.5
CVSS 4.0 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send crafted request to /api/v1/editor/ endpoint
  2. Delivery
    Inject SQL payload in unvalidated parameter
  3. Exploit
    Bypass incomplete fix validation
  4. Execution
    Execute arbitrary SQL queries
  5. Impact
    Access or modify database contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Remote unauthenticated attacker can exploit SQL injection in eosphoros-ai db-gpt versions up to 0.7.5 via the /api/v1/editor/ endpoint. No authentication, user interaction, or special configuration required. Default installations are vulnerable.

Impact

This vulnerability presents significant real-world risk based on multiple signals. The CVSS 3.1 score of 7.3 (High) reflects a network-accessible attack vector requiring no privileges or user interaction (AV:N/AC:L/PR:N/UI:N), with impacts to confidentiality, integrity, and availability all rated Low (C:L/I:L/A:L). The attack complexity is Low, making exploitation straightforward. Critically, a public proof-of-concept exploit is available on Huntr (https://huntr.com/bounties/e32fda74-ca83-431c-8de8-08274ba686c9), significantly lowering the barrier to exploitation. The vendor's non-responsiveness to early disclosure attempts raises concerns about patch availability and ongoing support. SQL injection attacks are well-understood and highly automatable, making this vulnerability a practical target for both opportunistic scanning and targeted attacks. The combination of public exploit code, network accessibility, and no authentication requirement elevates this beyond a theoretical concern to an immediate priority for organizations running affected versions.

Exploit ScenarioDerived

An unauthenticated remote attacker discovers the publicly available proof-of-concept exploit on Huntr and adapts it to target an internet-exposed DB-GPT instance. By sending specially crafted HTTP requests to the /api/v1/editor/ endpoint with malicious SQL payloads, the attacker successfully bypasses authentication checks, extracts sensitive database records including user credentials and proprietary AI model configurations, and potentially modifies or deletes critical data. The low attack complexity and availability of working exploit code enable even moderately skilled attackers to successfully compromise vulnerable instances within minutes of discovery.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 20, 2026

SQL injection in eosphoros-ai db-gpt versions up to 0.7.5 allows unauthenticated remote attackers to manipulate the /api/v1/editor/ endpoint and execute arbitrary database queries. Public exploit code is available for this vulnerability, and no patch has been released despite vendor notification. This vulnerability impacts confidentiality, integrity, and availability of affected systems.

Earlier versions of this analysis (1)
v1 Mar 20, 2026 - 20:15 CVSS 7.3

A SQL injection vulnerability exists in eosphoros-ai DB-GPT up to version 0.7.5, affecting the /api/v1/editor/ endpoint. This flaw represents an incomplete fix from a previous vulnerability, allowing remote attackers to execute arbitrary SQL commands without authentication. A public proof-of-concept exploit is available via Huntr, significantly increasing the risk of active exploitation.

RemediationAI

Organizations should immediately upgrade DB-GPT to a version newer than 0.7.5 if available, though vendor non-responsiveness suggests a patch may not exist. Until an official fix is released, implement compensating controls: restrict network access to the /api/v1/editor/ endpoint using firewall rules or API gateway policies to allow only trusted IP ranges; deploy a web application firewall (WAF) with SQL injection detection rules to filter malicious requests; implement input validation and sanitization at the application or reverse proxy layer; monitor database and application logs for SQL injection attempts referencing the /api/v1/editor/ path. Given the vendor's lack of response, organizations with high-risk profiles should consider migrating to alternative solutions or forking the open-source project to apply their own security fixes. Reference the Huntr bounty disclosure at https://huntr.com/bounties/e32fda74-ca83-431c-8de8-08274ba686c9 for technical details on the vulnerability mechanism.

Affected VersionsENISA

db-gpt 0.7.0
db-gpt 0.7.5
db-gpt 0.7.4
db-gpt 0.7.2
db-gpt 0.7.1
db-gpt 0.7.3

Affected Packages

euvd db_gpt no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

DB-GPT is an AI-native data application development framework by eosphoros-ai. The vulnerability is classified as CWE-89 (SQL Injection), indicating improper neutralization of special SQL query elements. The flaw specifically affects the /api/v1/editor/ API endpoint and represents an incomplete remediation attempt from a prior security issue. The affected product is identified via CPE cpe:2.3:a:eosphoros-ai:db-gpt:*:*:*:*:*:*:*:* for all versions through 0.7.5. SQL injection vulnerabilities occur when user-supplied input is incorporated into SQL queries without proper sanitization or parameterization, allowing attackers to manipulate database queries and potentially access, modify, or delete data.

Know when Db Gpt gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

5
CVSS changed
Apr 29, 2026 - 01:11 NVD
6.9 (MEDIUM) 5.5 (MEDIUM)
Severity Changed
Apr 22, 2026 - 21:37 NVD
HIGH MEDIUM
CVSS changed
Apr 22, 2026 - 21:37 NVD
7.3 (HIGH) 6.9 (MEDIUM)
PoC Detected
Mar 23, 2026 - 14:32 vuln.today
Public exploit code
CVE Published
Mar 20, 2026 - 20:02 nvd
HIGH 7.3

DescriptionCVE.org

A flaw has been found in eosphoros-ai db-gpt up to 0.7.5. This vulnerability affects unknown code of the file /api/v1/editor/ of the component Incomplete Fix. This manipulation causes sql injection. It is possible to initiate the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Executive ViewAI

Why It Matters

A critical SQL injection vulnerability in DB-GPT version 0.7.5 allows unauthenticated attackers to execute arbitrary database commands. With a public exploit available and no patch currently available, any organization running this application faces immediate risk of data breach, unauthorized access, and potential system compromise.

Business Impact: Severe
Compensating Controls

Implement WAF rules to detect and block SQL injection patterns on the /api/v1/editor/ endpoint; restrict network access to this endpoint using firewall rules (whitelist only authorized IP ranges); disable the /api/v1/editor/ endpoint if not critical to operations; implement database-level access controls limiting DB-GPT service account privileges; enable comprehensive database activity logging and alerting; consider air-gapping affected systems until patch availability; implement intrusion detection signatures for SQL injection exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

More in Db Gpt

View all
CVE-2024-10902 CRITICAL POC
9.8 Mar 20

In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /v1/personal/agent/upload` is vulnerable to Arbitrary File Uplo

CVE-2024-10835 CRITICAL POC
9.8 Mar 20

In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /api/v1/editor/sql/run` allows execution of arbitrary SQL queri

CVE-2026-77933 CRITICAL POC
9.3 Oct 20

DB-GPT through 0.8.2 ships a default docker-compose.yml that hardcodes the MySQL root password and publishes port 3306 o

CVE-2026-77932 CRITICAL POC
9.3 Oct 20

Unauthenticated remote code execution in DB-GPT through 0.8.2 allows remote attackers to reach the /api/v1/chat/react-ag

CVE-2024-10833 CRITICAL POC
9.1 Mar 20

eosphoros-ai/db-gpt version 0.6.0 is vulnerable to an arbitrary file write through the knowledge API. Rated critical sev

CVE-2024-10831 CRITICAL POC
9.1 Mar 20

In eosphoros-ai/db-gpt version 0.6.0, the endpoint for uploading files is vulnerable to absolute path traversal. Rated c

CVE-2024-10834 CRITICAL POC
9.1 Mar 20

eosphoros-ai/db-gpt version 0.6.0 contains a vulnerability in the RAG-knowledge endpoint that allows for arbitrary file

CVE-2024-10830 HIGH POC
8.2 Mar 20

A Path Traversal vulnerability exists in the eosphoros-ai/db-gpt version 0.6.0 at the API endpoint `/v1/resource/file/de

CVE-2025-0452 HIGH POC
8.2 Mar 20

eosphoros-ai/DB-GPT version latest is vulnerable to arbitrary file deletion on Windows systems via the '/v1/agent/hub/up

CVE-2024-10906 HIGH POC
8.1 Mar 20

In version 0.6.0 of eosphoros-ai/db-gpt, the `uvicorn` app created by `dbgpt_server` uses an overly permissive instance

CVE-2025-6772 MEDIUM POC
5.5 Jun 27

Path traversal in DB-GPT versions 0.7.0 through 0.7.2 allows unauthenticated remote attackers to read or write files out

CVE-2026-80104 CRITICAL
9.3 Aug 25

Unauthenticated arbitrary file write in DB-GPT 0.8.0 lets remote attackers achieve remote code execution through the ski

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy