EUVD-2026-55801
GHSA-vm6h-rfrh-ph3m
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAuthenticate with low-privilege account
-
DeliveryEdit SQText dashboard widget via TinyMCE
-
ExploitInject malicious HTML/JS payload
-
InstallPayload persisted server-side
-
C2Victim loads dashboard page
-
Executev-html renders unsanitized payload
-
ImpactArbitrary JS executes in victim browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker must hold a valid low-privilege SQLBot account with permission to modify dashboard text widget content (PR:L confirmed by CVSS 4.0 vector). The attack requires passive victim interaction - a second authenticated user must load the dashboard containing the injected widget (UI:P). There is no requirement for a non-default configuration; any SQLBot deployment where multiple users share dashboard access is exposed. Exploitation is limited to users who view the compromised dashboard - impact does not extend to the server or underlying database. Deployments where dashboard edit access is restricted to administrators, or where SQLBot is single-user, are not practically exploitable. |
| Impact | The CVSS 4.0 score of 5.1 is appropriate and reflects the constrained impact. The vector confirms subsequent-system impact only (SC:L/SI:L, VC:N/VI:N/VA:N), meaning only victims' browser sessions are affected, not the underlying server. PR:L confirms that exploitation is gated behind authenticated, low-privilege access - unauthenticated exploitation is not possible. UI:P requires a victim to passively view the dashboard, which is a realistic condition in a shared dashboard environment. Publicly available exploit code exists (GitHub issue #1308), which lowers the bar for abuse. The absence from CISA KEV suggests no confirmed widespread in-the-wild exploitation at time of analysis. EPSS data was not provided, so exploitation probability cannot be quantified; however, the combination of a public POC and authenticated-user-level prerequisite places this in a moderate-priority class for organizations with shared dashboard access. For single-tenant or tightly access-controlled deployments, risk is further reduced. |
| Exploit ScenarioDerived | An authenticated low-privilege SQLBot user with dashboard edit access navigates to a shared dashboard, edits an SQText widget, and submits a payload such as an image onerror tag or script tag through the TinyMCE interface. The payload is stored server-side and rendered via v-html to every subsequent dashboard viewer. Publicly available exploit code exists via GitHub issue #1308, making this straightforward to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 10, 2026
Stored cross-site scripting in SQLBot's SQText dashboard component allows any authenticated low-privilege user who can edit dashboard widgets to inject persistent HTML and JavaScript that executes in the browser of every user who views the affected dashboard. All versions through 1.10.0 are affected per CPE data (cpe:2.3:a:dataease:sqlbot:*:*:*:*:*:*:*:*), with the root cause confirmed by source code evidence as Vue's v-html directive rendering unsanitized TinyMCE output. No public exploit identified at time of analysis via active exploitation (CISA KEV), though publicly available exploit code exists via GitHub issue #1308, and a vendor-released patch is available as of commit c3f40a5.
RemediationAI
Vendor-released patch: commit c3f40a5 (upstream fix available via PR/commit; released patched version not independently confirmed beyond the commit). Upgrade by pulling from commit c3f40a5c05a53253b2924765b02b83f6a819948f or later from https://github.com/dataease/SQLBot/commit/c3f40a5c05a53253b2924765b02b83f6a819948f. For deployments unable to patch immediately, the most effective compensating control is restricting dashboard widget edit permissions to fully trusted users only - reducing the attacker population to administrators eliminates the low-privilege exploitation path, though it limits collaborative dashboard authoring. Blocking or disabling the SQText widget type entirely removes the attack surface at the cost of losing rich-text dashboard functionality. Do not rely on input filtering at the TinyMCE editor layer alone, as the underlying issue is client-side rendering without DOMPurify sanitization.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SQLBot is a Vue.js-based SQL analytics and dashboard product by dataease. The vulnerable component is the SQText text widget in the dashboard frontend (frontend/src/views/dashboard/components/sq-text/index.vue). The widget uses TinyMCE as a rich-text editor and binds its output to the DOM using Vue's v-html directive, which renders raw HTML without any sanitization. This directly maps to CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically the stored variant: attacker-controlled content is persisted server-side and replayed to all subsequent dashboard viewers. The fix confirmed in PR #1309 replaces v-html with v-dompurify-html, applying DOMPurify client-side sanitization before DOM insertion. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P) confirms network delivery with no special attack conditions and passive victim interaction.
Know when Sqlbot gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Stored XSS requires low-privilege dashboard edit access (PR:L), triggers on victim page view (UI:R), and affects other users' browser sessions via scope change (S:C); no availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
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.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
SQLBot is an intelligent data query system based on a large language model and RAG. [CVSS 6.1 MEDIUM]
Prompt injection in SQLBot 1.7.0 and earlier allows authenticated attackers to execute arbitrary SQL statements through
Remote code execution in SQLBot 1.5.0 and below allows authenticated users to inject malicious prompts through unsanitiz
SQLBot, an intelligent data query system based on large language models and RAG, contains a critical SQL injection vulne
Cross-workspace IDOR in SQLBot (DataEase) versions prior to 1.8.0 allows authenticated low-privilege users to read and m
A Server-Side Request Forgery (SSRF) vulnerability in SQLBot, an intelligent data query system based on large language m
Authenticated workspace members in DataEase SQLBot through 1.10.1 can rename and rewrite other users' private dashboards
A vulnerability was found in Dataease SQLBot up to 1.5.1. This impacts the function validateEmbedded of the file backend
A vulnerability has been found in Dataease SQLBot up to 1.4.0. This affects an unknown function of the file backend/apps
Server-side request forgery (SSRF) in Dataease SQLBot up to version 1.6.0 allows high-privileged remote attackers to man
Stored cross-site scripting in SQLBot prior to 1.9.0 lets an authenticated user with logo-upload privileges persist a ma
Exploit-DB