dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4504

HIGH · 7.3 CVSS v3.1 Published 2026-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in eosphoros-ai db-gpt versions up to 0.7.5 affecting the /api/v1/editor/ endpoint. The vulnerability is described as stemming from an 'Incomplete Fix,' suggesting a prior remediation attempt that did not fully address the SQL injection flaw. Attack can be exploited remotely.

MitigationReplace any incomplete prior fix with proper parameterized queries or prepared statements for all database operations in the /api/v1/editor/ endpoint; implement comprehensive input validation to prevent SQL injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the db-gpt installation
    Locate the db-gpt application directory or check the installed package version using package managers or the application's startup logs
    Affected if The application is eosphoros-ai db-gpt and the exact version cannot be determined or is 0.7.5 or lower
  2. Check the installed version against affected range
    Run the command to retrieve the db-gpt version (such as 'pip show db-gpt' or check version files in the installation directory) and compare it to the affected range of versions up to 0.7.5
    Affected if The installed version is 0.7.5 or any version lower than 0.7.5
  3. Determine if the vulnerable endpoint is exposed
    Review the application's routing configuration or server setup to confirm whether the /api/v1/editor/ endpoint is accessible (check route definitions in the API configuration files)
    Affected if The /api/v1/editor/ endpoint is exposed and reachable from the network or user-facing interface
  4. Inspect database operations in the editor endpoint
    Examine the source code handling the /api/v1/editor/ endpoint to identify any database query construction that incorporates user input without proper parameterized queries or prepared statements
    Affected if User-supplied input from the /api/v1/editor/ endpoint is directly concatenated into SQL queries without sanitization or parameterization
  5. Verify presence of prior incomplete fix
    Search the codebase for any existing SQL injection mitigation attempts in the /api/v1/editor/ endpoint handlers and assess whether they fully prevent SQL injection or have gaps
    Affected if A prior incomplete fix exists that does not properly use parameterized queries or comprehensive input validation for all database operations in the endpoint

A user is affected if they are running db-gpt version 0.7.5 or lower with the /api/v1/editor/ endpoint exposed and user input flowing to SQL queries without proper parameterization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace any incomplete prior fix with proper parameterized queries or prepared statements for all database operations in the /api/v1/editor/ endpoint; implement comprehensive input validation to prevent SQL injection.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4504 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data