Quick answers
- Is CVE-2026-50030 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50030 being exploited in the wild.
- How severe is CVE-2026-50030?
- Informational severity, with a CVSS score of 7.1, published 15 July 2026.
- Which products and versions are affected?
- DataEase < 2.10.23.
- Is there a fix for CVE-2026-50030?
- A patch was published on 2026-05-28: Version 2.10.23 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-50030 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-50030?
- Check whether you run DataEase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An SQL injection vulnerability exists in DataEase prior to version 2.10.23 due to improper neutralization of user-provided SQL in the preview functionality. The endpoint `/de2api/datasetData/previewSql` accepts a `PreviewSqlDTO` object containing Base64-encoded SQL. The backend decodes this input and passes it to `CalciteProvider.fetchResultField`, which executes the query via `prepareStatement(...).executeQuery()` without sufficient validation. Furthermore, the permission check in `CorePermissionManage.checkAuth` was found to return 'true' unconditionally in affected versions, allowing attackers to query any reachable datasource table and receive the results in the API response.
Affected products
- DataEase DataEase < 2.10.23
Timeline
- 2026-05-28: patched: Version 2.10.23 released
- 2026-05-28: advisory: GitHub Security Advisory published
- 2026-07-15: disclosed: NVD publication date