# CVE-2026-33122: DataEase has SQL Injection via Datasource Management

> An authenticated attacker can inject arbitrary SQL commands via the datasource update API to extract database information.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2026
- **Updated:** 17 Apr 2026
- **Also known as:** GHSA-28vg-3hv7-w92f

## What is CVE-2026-33122?

CVE-2026-33122 is a high-severity SQL injection vulnerability in Dataease Dataease, published on 16 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-33122?

It affects 1 product.


Products: Dataease Dataease.

## How do I fix CVE-2026-33122?

No fix has been published for CVE-2026-33122 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33122 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33122 exists.

## Other vulnerabilities in Dataease Dataease

- [CVE-2024-57707](https://insights.sbomify.com/CVE-2024-57707/): Code injection in n/a (critical 9.8)
- [CVE-2024-46997](https://insights.sbomify.com/CVE-2024-46997/): DataEase's H2 datasource has a remote command execution risk (critical 9.8)
- [CVE-2023-33963](https://insights.sbomify.com/CVE-2023-33963/): DataEase data source has deserialization vulnerability (critical 9.8)
- [CVE-2023-28437](https://insights.sbomify.com/CVE-2023-28437/): SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed (critical 9.8)
- [CVE-2022-39312](https://insights.sbomify.com/CVE-2022-39312/): Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33122 and fix it if it is affected.

What it is: CVE-2026-33122 is a high-severity SQL injection vulnerability in Dataease Dataease, published on 16 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33122 exists.

Affected product: Dataease Dataease. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33122/ (Markdown: https://insights.sbomify.com/CVE-2026-33122/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33122
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33122
- OSV: https://osv.dev/vulnerability/CVE-2026-33122

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33122/
Summaries are generated and may contain mistakes; the official description above is the record.