dbcve.org
DataeaseApplication

CVE-2026-33082

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 analysis tool. Versions 2.10.20 and below contain a SQL injection vulnerability in the dataset export functionality. The expressionTree parameter in POST /de2api/datasetTree/exportDataset is deserialized into a filtering object and passed to WhereTree2Str.transFilterTrees for SQL translation, where user-controlled values in "like" filter terms are directly concatenated into SQL fragments without sanitization. An attacker can inject arbitrary SQL commands by escaping the string literal in the filter value, enabling blind SQL injection through techniques such as time-based extraction of 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

DataEase versions 2.10.20 and below have a SQL injection vulnerability in the dataset export endpoint (POST /de2api/datasetTree/exportDataset). The expressionTree parameter is deserialized and passed to WhereTree2Str.transFilterTrees for SQL translation, where user-controlled values in 'like' filter terms are directly concatenated into SQL without sanitization, allowing arbitrary SQL command injection via blind time-based techniques.

MitigationUpgrade to DataEase version 2.10.21 or later to remediate this vulnerability. If immediate upgrade is not possible, consider restricting access to the affected API endpoint via network controls or WAF rules until the upgrade can be completed.

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
    Locate the DataEase installation and determine its version number (typically visible in the application UI header, admin panel, or deployment metadata)
    Affected if Installed version is 2.10.20 or lower (any version below 2.10.21)
  2. Confirm endpoint exposure
    Verify that the POST /de2api/datasetTree/exportDataset endpoint is accessible from your network (check reverse proxy, API gateway, or firewall rules)
    Affected if The endpoint is externally or internally accessible without network restrictions
  3. Check dataset export feature status
    Inspect DataEase configuration or admin settings to determine if dataset export functionality is enabled for users
    Affected if Dataset export feature is enabled and users have permissions to use it
  4. Review access logs for the affected endpoint
    Search application or proxy logs for requests to /de2api/datasetTree/exportDataset, particularly POST requests containing the expressionTree parameter
    Affected if Unexplained or anomalous requests to this endpoint are found in logs
  5. Inspect database query logs
    Enable and review database-level query logging to look for suspicious SQL patterns, especially time-based blind injection attempts (e.g., SLEEP() commands) originating from DataEase application queries
    Affected if Database logs show unexpected SQL constructs or time-based delays in queries

You are affected if your DataEase version is 2.10.20 or below AND the dataset export endpoint is accessible to users or attackers without additional network controls.

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 to remediate this vulnerability. If immediate upgrade is not possible, consider restricting access to the affected API endpoint via network controls or WAF rules until the upgrade can be completed.

Recommended fix High confidence

2.10.21

  1. 1. Back up the current Dataease installation and database before upgrading.
  2. 2. Upgrade Dataease to version 2.10.21 or later.
  3. 3. Verify the upgrade was successful by checking the Dataease version in the admin interface.
  4. 4. Test the dataset export functionality to confirm the vulnerability is resolved.
  5. 5. Monitor logs for any SQL injection attempts that may have targeted this endpoint.

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

Fix this in Dataease Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33082 — 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-33082 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