CVE-2026-53556: 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, the POST /api/v1/datasource/previewData endpoint in backend/apps/datasource/crud/datasource.py incorporates the client-controlled table_name value into generated SQL without safe identifier handling. An authenticated user can configure a datasource for SQLBot's internal PostgreSQL service and submit a crafted table_name that remains a SELECT operation under the read-only policy while invoking pg_read_file(), pg_read_binary_file(), or pg_ls_dir(). In the default tested trusted loopback authentication configuration, the internal connection accepts invalid credentials and executes with PostgreSQL superuser privileges, allowing filesystem content such as /etc/hosts and /etc/passwd to be returned in the previewData API response and potentially exposing configuration, credentials, authentication secrets, and source code. This issue is fixed in version 1.9.0.
AI Analysis
Technical Summary
SQLBot, an intelligent Text-to-SQL system, contains a SQL injection vulnerability (CWE-89) in versions before 1.9.0. The vulnerability exists in the POST /api/v1/datasource/previewData endpoint within backend/apps/datasource/crud/datasource.py, where the client-controlled table_name parameter is incorporated into SQL queries without safe identifier handling. An authenticated user can exploit this to invoke PostgreSQL functions such as pg_read_file(), pg_read_binary_file(), or pg_ls_dir() under a read-only policy, but due to the default trusted loopback authentication accepting invalid credentials, the internal PostgreSQL connection runs with superuser privileges. This enables reading sensitive filesystem files like /etc/hosts and /etc/passwd, potentially exposing configuration, credentials, authentication secrets, and source code. The vulnerability is resolved in SQLBot version 1.9.0.
Potential Impact
An authenticated attacker can exploit this SQL injection to read arbitrary files on the server filesystem via PostgreSQL superuser privileges, potentially exposing sensitive information including configuration files, credentials, authentication secrets, and source code. The vulnerability requires authenticated access and has a medium severity score (CVSS 6.0). There are no known exploits in the wild.
Mitigation Recommendations
Upgrade SQLBot to version 1.9.0 or later, where this SQL injection vulnerability is fixed. Until then, restrict access to the affected endpoint to trusted users only and avoid configurations that allow the internal PostgreSQL connection to accept invalid credentials with superuser privileges. Patch status is confirmed fixed in version 1.9.0.
CVE-2026-53556: 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, the POST /api/v1/datasource/previewData endpoint in backend/apps/datasource/crud/datasource.py incorporates the client-controlled table_name value into generated SQL without safe identifier handling. An authenticated user can configure a datasource for SQLBot's internal PostgreSQL service and submit a crafted table_name that remains a SELECT operation under the read-only policy while invoking pg_read_file(), pg_read_binary_file(), or pg_ls_dir(). In the default tested trusted loopback authentication configuration, the internal connection accepts invalid credentials and executes with PostgreSQL superuser privileges, allowing filesystem content such as /etc/hosts and /etc/passwd to be returned in the previewData API response and potentially exposing configuration, credentials, authentication secrets, and source code. This issue is fixed in version 1.9.0.
CVSS v4.0
Score 6.0medium
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, contains a SQL injection vulnerability (CWE-89) in versions before 1.9.0. The vulnerability exists in the POST /api/v1/datasource/previewData endpoint within backend/apps/datasource/crud/datasource.py, where the client-controlled table_name parameter is incorporated into SQL queries without safe identifier handling. An authenticated user can exploit this to invoke PostgreSQL functions such as pg_read_file(), pg_read_binary_file(), or pg_ls_dir() under a read-only policy, but due to the default trusted loopback authentication accepting invalid credentials, the internal PostgreSQL connection runs with superuser privileges. This enables reading sensitive filesystem files like /etc/hosts and /etc/passwd, potentially exposing configuration, credentials, authentication secrets, and source code. The vulnerability is resolved in SQLBot version 1.9.0.
Potential Impact
An authenticated attacker can exploit this SQL injection to read arbitrary files on the server filesystem via PostgreSQL superuser privileges, potentially exposing sensitive information including configuration files, credentials, authentication secrets, and source code. The vulnerability requires authenticated access and has a medium severity score (CVSS 6.0). There are no known exploits in the wild.
Mitigation Recommendations
Upgrade SQLBot to version 1.9.0 or later, where this SQL injection vulnerability is fixed. Until then, restrict access to the affected endpoint to trusted users only and avoid configurations that allow the internal PostgreSQL connection to accept invalid credentials with superuser privileges. Patch status is confirmed fixed in version 1.9.0.
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: 6aac5fee55bf5e2cf5f75525
Added to database: 09/17/2026, 21:47:26 UTC
Last enriched: 09/17/2026, 22:02:08 UTC
Last updated: 09/18/2026, 01:37:34 UTC
Views: 8
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.