CVE-2026-4504
Published: 20 March 2026
Summary
CVE-2026-4504 is a medium-severity Injection (CWE-74) vulnerability. Its CVSS base score is 6.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 13.1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
This vulnerability is AI-related — categorised as LLM Application Platforms; in the Data-Related Vulnerabilities risk domain.
The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).
Deeper analysis
CVE-2026-4504 is a SQL injection vulnerability (CWE-74, CWE-89) in eosphoros-ai db-gpt versions up to 0.7.5. The flaw affects unknown code in the /api/v1/editor/ file within the Incomplete Fix component, allowing malicious manipulation that triggers SQL injection.
Attackers can exploit this remotely without authentication (AV:N/AC:L/PR:N/UI:N), requiring low complexity and no user interaction. Exploitation enables low impacts on confidentiality, integrity, and availability (C:L/I:L/A:L), as reflected in the CVSS v3.1 base score of 7.3 (High), potentially allowing unauthorized database access or manipulation.
Advisories from VulDB and Huntr indicate that an exploit has been published and may be actively used. The vendor was contacted early for responsible disclosure but provided no response, and no patches or mitigations are mentioned in available references.
This vulnerability carries notable context due to the AI/ML relevance of db-gpt and the public availability of the exploit, heightening risks for deployments prior to version 0.7.5.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13804
Vulnerability details
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…
more
has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
- CWE(s)
AI Security AnalysisAI
- AI Category
- LLM Application Platforms
- Risk Domain
- Data-Related Vulnerabilities
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: ai, gpt
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SQL injection in unauthenticated public-facing web API (/api/v1/editor/) directly enables remote exploitation of the application per T1190, resulting in unauthorized DB access/manipulation.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly prevents SQL injection in the /api/v1/editor/ endpoint by requiring comprehensive input validation and error handling for database queries.
Addresses the incomplete fix in db-gpt by mandating timely identification, reporting, and correction of the SQL injection flaw.
Mitigates remote exploitation via web application firewall rules at system boundaries to block SQL injection payloads targeting the vulnerable API.