CVE-2026-33122
SQL Injection in DataEase API Allows Database Information Disclosure
Publication date: 2026-04-16
Last updated on: 2026-04-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dataease | dataease | to 2.10.21 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in DataEase versions 2.10.20 and below, where the API datasource update process improperly handles the deTableName field. Specifically, when a new table definition is added via the /de2api/datasource/update endpoint, the deTableName value is directly inserted into a CREATE TABLE SQL statement without sanitization or escaping. This allows an authenticated attacker to craft a deTableName that breaks out of the intended SQL identifier quoting, enabling error-based SQL injection to extract database information.
The issue has been fixed in version 2.10.21.
How can this vulnerability impact me? :
An attacker who is authenticated can exploit this vulnerability to perform SQL injection attacks, which may allow them to extract sensitive database information. This can lead to unauthorized data disclosure, potentially compromising the confidentiality and integrity of the data managed by the DataEase platform.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade DataEase to version 2.10.21 or later, where the SQL injection issue has been fixed.
Ensure that only authenticated users with appropriate privileges can access the /de2api/datasource/update API endpoint to reduce risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows an authenticated attacker to perform error-based SQL injection, potentially extracting sensitive database information. This exposure of sensitive data could lead to non-compliance with data protection standards and regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access.
Since the vulnerability enables unauthorized data extraction through SQL injection, it increases the risk of data breaches, which are subject to regulatory reporting and penalties under these standards.