dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-50030

HIGH · 7.1 CVSS v4.0 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click Patch available 5 weeks old

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 analysis tool. Prior to 2.10.23, DataEase SQL preview exposes DatasetDataApi.previewSql/previewSqlCheck through /de2api/datasetData/previewSql, accepts PreviewSqlDTO.sql, PreviewSqlDTO.datasourceId, and PreviewSqlDTO.isCross, then DatasetDataManage.previewSql stores decoded SQL in datasourceRequest.query and CalciteProvider.fetchResultField executes it with prepareStatement(...).executeQuery(), allowing arbitrary readable datasource tables to be queried and returned in preview responses. This issue is fixed in version 2.10.23.

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 prior to 2.10.23 contain an SQL injection vulnerability in the SQL preview endpoint /de2api/datasetData/previewSql. The endpoint accepts user-supplied SQL through PreviewSqlDTO.sql, stores it in datasourceRequest.query, and executes it via prepareStatement().executeQuery(), allowing attackers to query arbitrary readable datasource tables.

MitigationUpgrade DataEase to version 2.10.23 or later to patch the SQL injection vulnerability in the SQL preview functionality.

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

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 installation and version
    Locate the DataEase application and check its version number. This is typically visible in the UI footer, in the about section, or via administrative panels. Compare the installed version to the affected range (any version prior to 2.10.23).
    Affected if The installed version is 2.10.22 or earlier, or if the version cannot be determined but is known to be before 2.10.23.
  2. Verify the SQL preview endpoint exists
    Check if the endpoint /de2api/datasetData/previewSql is accessible. This can be confirmed by examining the deployed application's API routes or by reviewing the WAR/JAR file contents for the presence of the relevant controller handling this path.
    Affected if The endpoint /de2api/datasetData/previewSql exists in the deployment and accepts requests.
  3. Confirm dataset functionality is enabled
    Verify that the datasetData module or functionality is enabled in the DataEase configuration. This may be visible in the application settings, feature flags, or by checking if the dataset-related database tables or API handlers are active.
    Affected if The datasetData functionality is enabled and operational in the environment.
  4. Check user access to SQL preview feature
    Determine whether any configured users or roles have permissions to access the SQL preview functionality. Review role-based access control (RBAC) settings or authentication configuration to see if non-admin users can invoke the /de2api/datasetData/previewSql endpoint.
    Affected if Any authenticated or unauthenticated user can access the SQL preview endpoint.

A user is affected if DataEase version is prior to 2.10.23 AND the SQL preview endpoint /de2api/datasetData/previewSql is accessible and functional in their environment.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade DataEase to version 2.10.23 or later to patch the SQL injection vulnerability in the SQL preview functionality.

Recommended fix High confidence

2.10.23

  1. 1. Identify the current DataEase installation version by checking the application or deployment manifests.
  2. 2. Create a complete backup of the current DataEase installation including database and configuration files.
  3. 3. Stop the DataEase service to prevent data inconsistency during upgrade.
  4. 4. Upgrade DataEase to version 2.10.23 following the official upgrade documentation for your deployment method (Docker, Helm, or manual installation).
  5. 5. Start the DataEase service and verify it runs without errors.
  6. 6. Test the SQL preview functionality at /de2api/datasetData/previewSql to confirm the vulnerability is patched and the API functions correctly.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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