Skip to main content

DataEase CVE-2026-33122

| EUVDEUVD-2026-23290 HIGH
SQL Injection (CWE-89)
2026-04-16 GitHub_M
8.6
CVSS 4.0 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain authenticated DataEase account
  2. Delivery
    Send datasource update to /de2api/datasource/update
  3. Exploit
    Inject crafted deTableName into CREATE TABLE
  4. Execution
    Break identifier quoting, append SQL
  5. Persist
    Trigger error-based injection
  6. Impact
    Extract database information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated account with permission to create or update a datasource (CVSS PR:L). The concrete trigger is submitting a datasource update to /de2api/datasource/update that adds a new table definition, supplying a malicious deTableName value that breaks out of identifier quoting in the CREATE TABLE template handled by DatasourceSyncManage.createEngineTable. Limiting factors: valid credentials and datasource-management privileges are needed, exploitation is per-target and not automatable (SSVC Automatable:no), and only versions ≤ 2.10.20 are affected. No user interaction beyond the attacker's own request is required (UI:N).

Impact

Signals are mixed and lean toward moderate real-world priority. The CVSS 4.0 base of 8.6 (AV:N/AC:L/AT:N/PR:L/UI:N, VC:H/VI:H) reflects a network-reachable, low-complexity flaw with high confidentiality and integrity impact, and SSVC rates Technical Impact as 'total' - consistent with full read/exfiltration of the datastore. However, PR:L means valid authentication is required, SSVC marks Automatable:no (per-target exploitation, no spray-and-pray), and EPSS is only 0.03% (8th percentile), indicating no observed mass exploitation. Exploitation status is 'poc' in SSVC and it is NOT in CISA KEV, so this is a real, patchable weakness with demonstrated exploitability but no evidence of active in-the-wild use. Net: prioritize patching on internet-exposed or multi-tenant DataEase instances, but this is not a wormable, unauthenticated emergency.

Exploit ScenarioDerived

An authenticated DataEase user (or an attacker who has obtained low-privilege credentials) sends a datasource update to /de2api/datasource/update containing a new table whose deTableName is crafted to break out of the CREATE TABLE identifier quoting and append malicious SQL. The resulting database error messages leak query results, letting the attacker enumerate schemas and exfiltrate data. A proof-of-concept is indicated (SSVC exploitation: poc), and the low attack complexity (AC:L) makes reliable exploitation straightforward once access is obtained.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 24, 2026

SQL injection in DataEase (versions ≤ 2.10.20) lets an authenticated user run arbitrary SQL against the backing database through the API datasource update endpoint. The attacker-controlled deTableName field is dropped into a CREATE TABLE statement without escaping, yielding error-based injection that can extract database contents. A proof-of-concept is indicated by CISA SSVC, though EPSS remains very low (0.03%) and it is not on CISA KEV; fixed in 2.10.21.

RemediationAI

Vendor-released patch: 2.10.21 - upgrade to DataEase 2.10.21 or later, which fixes this along with several other SQL injection issues (CVE-2026-33082/33083/33084/33121/33207) disclosed in the same release. Note a breaking change: from 2.10.21 frontend user credential names gain a prefix (e.g. user.token becomes de_v2_user.token), which affects integrations such as SQLBot, so test dependent tooling before rollout. If immediate upgrade is not possible, restrict who can reach /de2api/datasource/update by limiting datasource-creation/update privileges to trusted administrators and placing the DataEase admin API behind network ACLs or a reverse proxy so only trusted operators can submit datasource configurations; the trade-off is reduced self-service datasource management for lower-trust users. Advisory: https://github.com/dataease/dataease/security/advisories/GHSA-28vg-3hv7-w92f ; release notes: https://github.com/dataease/dataease/releases/tag/v2.10.21.

Affected VersionsENISA

dataease < 2.10.21

Affected Packages

euvd dataease fix: 2.10.21

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

DataEase is an open-source business-intelligence and data-visualization platform (analogous to Metabase/Superset) that connects to external databases and materializes definitions into its own engine tables. The flaw (CWE-89, Improper Neutralization of Special Elements in an SQL Command) sits in DatasourceSyncManage.createEngineTable: when a datasource update via /de2api/datasource/update adds a new table definition, the user-supplied deTableName is concatenated into a CREATE TABLE statement template as an identifier with no sanitization or identifier-quote escaping. Because deTableName is treated as a trusted identifier rather than parameterized or validated, a crafted value can break out of the quoting context and append attacker SQL. CPE cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:* confirms the affected product line.

Know when Dataease 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

GitHub Advisory PRIMARY 8.6 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 8.1 HIGH

Network endpoint reachable with valid low-privilege datasource credentials (PR:L, AV:N, AC:L); arbitrary SQL enables data extraction and modification (C:H/I:H) but no availability impact stated (A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

4
Patch released
Apr 20, 2026 - 16:40 nvd
Patch available
Patch available
Apr 16, 2026 - 20:31 EUVD
CVSS changed
Apr 16, 2026 - 20:22 NVD
8.6 (HIGH)
CVE Published
Apr 16, 2026 - 19:24 nvd
HIGH 8.6

DescriptionGitHub Advisory

DataEase is an open-source data visualization and analytics platform. Versions 2.10.20 and below contain a SQL injection vulnerability in the API datasource update process. When a new table definition is added during a datasource update via /de2api/datasource/update, the deTableName field from the user-submitted configuration is passed to DatasourceSyncManage.createEngineTable, where it is substituted into a CREATE TABLE statement template without any sanitization or identifier escaping. An authenticated attacker can inject arbitrary SQL commands by crafting a deTableName that breaks out of identifier quoting, enabling error-based SQL injection that can extract database information. This issue has been fixed in version 2.10.21.

Executive ViewAI

Why It Matters

DataEase versions 2.10.20 and earlier contain a SQL injection vulnerability in the API datasource update endpoint that allows authenticated users to extract sensitive data from the underlying database. Organizations must upgrade immediately to prevent unauthorized database access by internal users or compromised service accounts.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Prevalence
Medium
popular open-source BI platform, common but not universally deployed
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2025-49003 CRITICAL POC
9.8 Jun 26

DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.11, a threat actor m

CVE-2025-49002 CRITICAL POC
9.8 Jun 03

Auth bypass in DataEase via CVE-2025-49001 patch evasion. PoC available.

CVE-2025-49001 CRITICAL POC
9.8 Jun 03

Auth bypass in DataEase BI tool before 2.10.10.

CVE-2025-53005 CRITICAL POC
9.8 Jul 01

A remote code execution vulnerability in DataEase (CVSS 9.8). Risk factors: public PoC available.

CVE-2025-53004 CRITICAL POC
9.8 Jun 30

A remote code execution vulnerability in DataEase (CVSS 9.8). Risk factors: public PoC available.

CVE-2025-53006 CRITICAL POC
9.8 Jul 02

A remote code execution vulnerability in DataEase (CVSS 9.8). Risk factors: public PoC available.

CVE-2026-23958 CRITICAL POC
9.8 Jan 22

DataEase data visualization tool prior to 2.10.19 uses MD5-hashed passwords without salting, allowing attackers to crack

CVE-2024-46997 CRITICAL POC
9.8 Sep 23

DataEase is an open source data visualization analysis tool. Rated critical severity (CVSS 9.8), this vulnerability is r

CVE-2023-37258 CRITICAL POC
9.8 Jul 25

DataEase is an open source data visualization analysis tool. Rated critical severity (CVSS 9.8), this vulnerability is r

CVE-2023-33963 CRITICAL POC
9.8 Jun 01

DataEase is an open source data visualization and analysis tool. Rated critical severity (CVSS 9.8), this vulnerability

CVE-2023-28437 CRITICAL POC
9.8 Mar 25

Dataease is an open source data visualization and analysis tool. Rated critical severity (CVSS 9.8), this vulnerability

CVE-2022-39312 CRITICAL POC
9.8 Oct 25

Dataease is an open source data visualization analysis tool. Rated critical severity (CVSS 9.8), this vulnerability is r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy