dbcve.org
DataeaseApplication

CVE-2026-33122

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-16
Fix available
A fix is available. Upgrade to 2.10.21 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in DataEase versions 2.10.20 and below allows authenticated users to inject arbitrary SQL via the deTableName parameter in the /de2api/datasource/update endpoint. The user-supplied table name is directly concatenated into a CREATE TABLE statement without proper sanitization or identifier escaping in DatasourceSyncManage.createEngineTable, enabling error-based SQL injection to extract database information.

MitigationUpgrade to DataEase version 2.10.21 or later. If immediate patching is not feasible, implement API access controls to restrict the datasource/update endpoint to trusted, privileged users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DataeaseApplication
Affected:< 2.10.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DataEase version
    Check the installed DataEase version through the admin interface (typically at /system/about) or by querying the application startup logs for the version number
    Affected if Running version 2.10.20 or any version below 2.10.21
  2. Verify datasource/update endpoint accessibility
    Confirm the /de2api/datasource/update API endpoint is exposed and reachable in the deployment (check proxy configurations, network ACLs, or API gateway settings)
    Affected if The endpoint is externally accessible or accessible to untrusted users
  3. Check authentication enforcement on the endpoint
    Review the authentication and authorization configuration for the /de2api/datasource/update endpoint to verify whether it properly enforces user authentication and privilege checks
    Affected if The endpoint can be accessed without proper authentication or by low-privilege authenticated users
  4. Confirm DatasourceSyncManage module is enabled
    Verify that the datasource synchronization functionality (DatasourceSyncManage) is enabled in the DataEase installation through the admin panel or configuration files
    Affected if The datasource sync feature is active and the createEngineTable method is in use

A user is affected if running DataEase version below 2.10.21 with the /de2api/datasource/update endpoint accessible to authenticated users who can supply the deTableName parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.21 or later
Fixed in 2.10.21
Interim mitigation

Upgrade to DataEase version 2.10.21 or later. If immediate patching is not feasible, implement API access controls to restrict the datasource/update endpoint to trusted, privileged users only.

Recommended fix High confidence

2.10.21

  1. Backup your Dataease installation and database before upgrading
  2. Upgrade Dataease to version 2.10.21 or later by following the official upgrade documentation
  3. After upgrade, verify the /de2api/datasource/update endpoint is functioning correctly
  4. Confirm the deTableName parameter is now properly sanitized and escaped before being used in SQL statements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dataease Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33122 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data