Approved changes feed: RSS · Atom

cpe:2.3:a:dataease:sqlbot:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorDataease (49a0f5ff-39a9-53d0-a220-9b602aa445ea)
ProductSqlbot (efb78020-b35b-541b-aec6-e6afa169dc42)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
pkg:github/dataease/sqlbot purl2cpe 2026-07-28 16:40:52.942776

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-72743 vulnerable 2026-09-16 04:33:09.057882 SQLBot 1.10.0 SQText Dashboard Component Stored XSS via v-html
MEDIUM (5.4)
SQLBot through 1.10.0, fixed in commit c3f40a5, contains a stored cross-site scripting vulnerability in the SQText dashboard component that renders TinyMCE output via v-html without sanitization. Attackers who can modify dashboard text widget content can inject arbitrary HTML and JavaScript that executes for all users viewing the dashboard.
Published: 2026-08-10T20:06:32.158Z
Updated: 2026-08-17T18:18:07.729Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-5417 vulnerable 2026-06-08 08:07:03.687465 Dataease SQLbot Elasticsearch es_engine.py get_es_data_by_http server-side request forgery
MEDIUM (4.7)
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.
Published: 2026-04-02T18:15:11.883Z
Updated: 2026-04-03T20:00:17.177Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-42463 vulnerable 2026-06-08 08:03:16.331607 SQLBot: Unauthorized Access Vulnerability
SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.8.0, SQLBot contains a Cross-Workspace IDOR (Insecure Direct Object Reference) and Authorization Bypass vulnerability in the /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema endpoints. An attacker can access and modify database schemas and data sources belonging to other tenants/workspaces. This vulnerability is fixed in 1.8.0.
Published: 2026-05-13T21:26:27.821Z
Updated: 2026-05-14T13:40:32.770Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-33324 vulnerable 2026-06-08 07:59:09.703687 SQLBot prompt injection allows arbitrary SQL execution and remote code execution
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.
Published: 2026-05-05T19:09:36.031Z
Updated: 2026-05-05T19:38:28.127Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-32950 vulnerable 2026-06-08 07:57:18.373143 SQLBot: RCE via SQL Injection in Excel Upload Endpoint
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.
Published: 2026-03-20T04:14:45.640Z
Updated: 2026-03-24T01:49:10.552Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-32949 vulnerable 2026-06-08 07:57:18.372698 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-32622 vulnerable 2026-06-08 07:57:17.768170 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-69285 vulnerable 2026-06-08 07:41:22.362475 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-15598 vulnerable 2026-06-08 07:06:36.523964 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-15597 vulnerable 2026-06-08 07:06:36.522813 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.