Skip to main content
VulnerabilityPublished

CVE-2026-4504: eosphoros-ai db-gpt · SQL Injection

Affects eosphoros-ai db-gptSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
eosphoros-aidb-gptAffected
  • 0.7.0 – 0.7.5
6 affected builds
Fixed in–

AI-suggested

  1. Immediately restrict network access to the /api/v1/editor/ endpoint by implementing IP whitelisting or VPN-only access to limit exposure.
  2. Deploy a web application firewall (WAF) with robust SQL injection detection and prevention rules tailored to the db-gpt API traffic.
  3. Conduct thorough input validation and sanitization on all parameters accepted by the /api/v1/editor/ endpoint, applying strict whitelisting of allowed characters and query structures.
  4. Monitor database logs and application logs for unusual or suspicious SQL queries indicative of injection attempts.
  5. If possible, isolate the vulnerable db-gpt instances in segmented network zones to contain potential exploitation impact.
  6. Engage with the vendor or community to track any forthcoming patches or updates and plan for prompt application once available.
  7. Consider deploying database activity monitoring tools that can alert on anomalous query patterns.
  8. Educate development and operations teams about the risks of SQL injection and secure coding practices to prevent similar vulnerabilities in future releases.
  9. If feasible, migrate to alternative or updated database management solutions that do not exhibit this vulnerability until an official patch is released.

Description

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.

References

Community reviews

Loading reviews…