CVE-2026-53557: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in dataease SQLBot
SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.9.0, an authenticated user can supply a crafted sheet["tableName"] value in the Excel datasource configuration submitted through POST /api/v1/datasource/, and SQLBot stores that value without safe identifier handling. When the same datasource is later removed through DELETE /api/v1/datasource/{id}, the stored value is interpolated into datasource cleanup SQL and executed by PostgreSQL. This second-order SQL injection can invoke PostgreSQL COPY TO PROGRAM and execute arbitrary operating-system commands with the privileges of the postgres process inside the SQLBot container. This issue is fixed in version 1.9.0.
AI Analysis
Technical Summary
SQLBot, an intelligent Text-to-SQL system, suffers from a second-order SQL injection vulnerability (CWE-89) in versions before 1.9.0. An authenticated user can submit a malicious tableName in the Excel datasource configuration via POST /api/v1/datasource/. This value is stored unsafely and later used in a DELETE /api/v1/datasource/{id} operation, where it is interpolated into a SQL cleanup command executed by PostgreSQL. This allows invocation of PostgreSQL's COPY TO PROGRAM feature, enabling arbitrary OS command execution with the privileges of the postgres process within the SQLBot container. The issue is resolved in version 1.9.0.
Potential Impact
Successful exploitation allows an authenticated user with low privileges to execute arbitrary operating system commands on the host running SQLBot with the privileges of the postgres process inside the container. This can lead to full system compromise of the container environment. The vulnerability requires authentication and has a high attack complexity due to the need to craft specific input and trigger the deletion operation.
Mitigation Recommendations
Upgrade SQLBot to version 1.9.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is documented. Users should apply this official fix to prevent exploitation.
CVE-2026-53557: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in dataease SQLBot
Description
SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.9.0, an authenticated user can supply a crafted sheet["tableName"] value in the Excel datasource configuration submitted through POST /api/v1/datasource/, and SQLBot stores that value without safe identifier handling. When the same datasource is later removed through DELETE /api/v1/datasource/{id}, the stored value is interpolated into datasource cleanup SQL and executed by PostgreSQL. This second-order SQL injection can invoke PostgreSQL COPY TO PROGRAM and execute arbitrary operating-system commands with the privileges of the postgres process inside the SQLBot container. This issue is fixed in version 1.9.0.
CVSS v4.0
Score 7.7high
Affected software
dataease
SQLBot
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
SQLBot, an intelligent Text-to-SQL system, suffers from a second-order SQL injection vulnerability (CWE-89) in versions before 1.9.0. An authenticated user can submit a malicious tableName in the Excel datasource configuration via POST /api/v1/datasource/. This value is stored unsafely and later used in a DELETE /api/v1/datasource/{id} operation, where it is interpolated into a SQL cleanup command executed by PostgreSQL. This allows invocation of PostgreSQL's COPY TO PROGRAM feature, enabling arbitrary OS command execution with the privileges of the postgres process within the SQLBot container. The issue is resolved in version 1.9.0.
Potential Impact
Successful exploitation allows an authenticated user with low privileges to execute arbitrary operating system commands on the host running SQLBot with the privileges of the postgres process inside the container. This can lead to full system compromise of the container environment. The vulnerability requires authentication and has a high attack complexity due to the need to craft specific input and trigger the deletion operation.
Mitigation Recommendations
Upgrade SQLBot to version 1.9.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is documented. Users should apply this official fix to prevent exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T18:13:07.263Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aac5fee55bf5e2cf5f75526
Added to database: 09/17/2026, 21:47:26 UTC
Last enriched: 09/17/2026, 22:01:41 UTC
Last updated: 09/18/2026, 02:19:11 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.