CVE-2026-33121 | DataEase up to 2.10.20 API deTableName sql injection

VDB-357952 · CVE-2026-33121 · GCVE-0-2026-33121 DATAEASE UP TO 2.10.20 API DETABLENAME SQL INJECTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.0 $0-$5k 1.31+ Summaryinfo A vulnerability classified as critical was found in DataEase up to 2.10.20. Affected by this issue is some unknown functionality of the component API. Executing a manipulation of the argument deTableName can lead to sql injection. This vulnerability is tracked as CVE-2026-33121. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised. Detailsinfo A vulnerability has been found in DataEase up to 2.10.20 and classified as critical. This vulnerability affects an unknown function of the component API. The manipulation of the argument deTableName with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes: 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 saving process. The deTableName field from the Base64-encoded datasource configuration is used to construct a DDL statement via simple string replacement without any sanitization or escaping of the table name. 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 such as the MySQL version. This issue has been fixed in version 2.10.21. The advisory is shared for download at github.com. This vulnerability was named CVE-2026-33121 since 03/17/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505. Upgrading to version 2.10.21 eliminates this vulnerability. Productinfo Name DataEase Version 2.10.0 2.10.1 2.10.2 2.10.3 2.10.4 2.10.5 2.10.6 2.10.7 2.10.8 2.10.9 2.10.10 2.10.11 2.10.12 2.10.13 2.10.14 2.10.15 2.10.16 2.10.17 2.10.18 2.10.19 2.10.20 Website Product: https://github.com/dataease/dataease/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 6.3 VulDB Meta Temp Score: 6.0 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Sql injection CWE: CWE-89 / CWE-74 / CWE-707 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: DataEase 2.10.21 Timelineinfo 03/17/2026 CVE reserved 04/16/2026 +29 days Advisory disclosed 04/16/2026 +0 days VulDB entry created 04/16/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-33121 (🔒) GCVE (CVE): GCVE-0-2026-33121 GCVE (VulDB): GCVE-100-357952 Entryinfo Created: 04/16/2026 21:32 Changes: 04/16/2026 21:32 (67) Complete: 🔍 Cache ID: 99:F2E:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸