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.
CVE-2026-53555 is a stored cross-site scripting (XSS) vulnerability in dataease SQLBot versions prior to 1.9.0. An authenticated user can upload an SVG image containing malicious JavaScript via a PATCH request. The application stores this SVG without sanitization and later serves it inline, allowing the embedded script to execute in the context of other users' sessions. This can lead to unauthorized actions and data access within the victim's session. The issue is fixed in version 1.9.0.
CVE-2026-53556 is an SQL injection vulnerability in dataease SQLBot prior to version 1.9.0. The issue occurs in the POST /api/v1/datasource/previewData endpoint, where the client-controlled table_name parameter is incorporated into SQL queries without proper safe identifier handling. This allows an authenticated user to execute read-only SELECT operations that can invoke PostgreSQL functions to read filesystem contents. In default configurations, the internal PostgreSQL connection accepts invalid credentials and runs with superuser privileges, potentially exposing sensitive files such as /etc/hosts and /etc/passwd. The vulnerability is fixed in version 1.9.0.
CVE-2026-53554 is a path traversal vulnerability in dataease SQLBot versions prior to 1.9.0. The issue occurs in the POST /api/v1/datasource/parseExcel endpoint, which improperly uses attacker-controlled multipart filename data to determine where uploaded files are stored. This allows an attacker to place malicious files in the Alembic migration directory, which are then executed during SQLBot startup or migration processing. The vulnerability is fixed in version 1.9.0.
SQLBot versions prior to 1.8.0 contain an authorization bypass vulnerability classified as CWE-639 (Authorization Bypass Through User-Controlled Key). This vulnerability affects the /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema endpoints, allowing an attacker with limited privileges to access and modify database schemas and data sources belonging to other tenants or workspaces. The issue is fixed in version 1.8.0. The CVSS 4.0 base score is 8.6, indicating a high severity vulnerability.
SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. In versions 1.7.0 and earlier, the Text2SQL chat interface is vulnerable to prompt injection. The user-provided question parameter is directly concatenated into the LLM prompt without filtering or escaping, and the SQL extracted from the LLM response is executed against the database without validation or sanitization. An authenticated attacker can craft a malicious question to manipulate the LLM into generating and executing arbitrary SQL statements. When connected to a PostgreSQL data source, this can lead to remote code execution via COPY FROM PROGRAM. This issue has been fixed in version 1.7.1.
A vulnerability was determined in Dataease SQLbot up to 1.6.0. This issue affects the function get_es_data_by_http of the file backend/apps/db/es_engine.py of the component Elasticsearch Handler. This manipulation of the argument address causes server-side request forgery. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 1.7.0 is capable of addressing this issue. You should upgrade the affected component. The vendor was contacted early about this disclosure.
SQLBot is an intelligent data query system based on a large language model and RAG. Versions prior to 1.7.0 contain a critical SQL Injection vulnerability in the /api/v1/datasource/uploadExcel endpoint that enables Remote Code Execution (RCE), allowing any authenticated user (even the lowest-privileged) to fully compromise the backend server. The root cause is twofold: Excel Sheet names are concatenated directly into PostgreSQL table names without sanitization (datasource.py#L351), and those table names are embedded into COPY SQL statements via f-strings instead of parameterized queries (datasource.py#L385-L388). An attacker can bypass the 31-character Sheet name limit using a two-stage technique—first uploading a normal file whose data rows contain shell commands, then uploading an XML-tampered file whose Sheet name injects a TO PROGRAM 'sh' clause into the SQL. Confirmed impacts include arbitrary command execution as the postgres user (uid=999), sensitive file exfiltration (e.g., /etc/passwd, /etc/shadow), and complete PostgreSQL database takeover. This issue has been fixed in version 1.7.0.
CVE-2026-32949 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in dataease SQLBot versions prior to 1.7.0. It allows unauthenticated attackers to exploit the /api/v1/datasource/check endpoint by configuring a malicious MySQL data source with the parameter extraJdbc="local_infile=1". During the backend's connectivity check, a rogue MySQL server can trigger a LOAD DATA LOCAL INFILE command, forcing the target server to read arbitrary local files and send their contents back to the attacker. This can lead to disclosure of sensitive system and application files such as /etc/passwd. The vulnerability requires no authentication or user interaction and affects the confidentiality of the server. It was fixed in version 1.7.0.
SQLBot is an intelligent data query system based on a large language model and RAG. Versions 1.5.0 and below contain a Stored Prompt Injection vulnerability that chains three flaws: a missing permission check on the Excel upload API allowing any authenticated user to upload malicious terminology, unsanitized storage of terminology descriptions containing dangerous payloads, and a lack of semantic fencing when injecting terminology into the LLM's system prompt. Together, these flaws allow an attacker to hijack the LLM's reasoning to generate malicious PostgreSQL commands (e.g., COPY ... TO PROGRAM), ultimately achieving Remote Code Execution on the database or application server with postgres user privileges. The issue is fixed in v1.6.0.
A vulnerability has been found in Dataease SQLBot up to 1.4.0. This affects an unknown function of the file backend/apps/system/api/assistant.py of the component API Endpoint. Such manipulation leads to improper access controls. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.5.0 mitigates this issue. The name of the patch is d640ac31d1ce64ce90e06cf7081163915c9fc28c. Upgrading the affected component is recommended. Multiple endpoints are affected. The vendor was contacted early about this disclosure.
SQLBot is an intelligent data query system based on a large language model and RAG. Versions prior to 1.5.0 contain a missing authentication vulnerability in the /api/v1/datasource/uploadExcel endpoint, allowing a remote unauthenticated attacker to upload arbitrary Excel/CSV files and inject data directly into the PostgreSQL database. The endpoint is explicitly added to the authentication whitelist, causing the TokenMiddleware to bypass all token validation. Uploaded files are parsed by pandas and inserted into the database via to_sql() with if_exists='replace' mode. The vulnerability has been fixed in v1.5.0. No known workarounds are available.