Quick answers
- Is CVE-2026-45535 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45535 being exploited in the wild.
- How severe is CVE-2026-45535?
- Informational severity, with a CVSS score of 8.7, published 15 July 2026.
- Which products and versions are affected?
- DataEase < 2.10.23.
- Is there a fix for CVE-2026-45535?
- A patch was published on 2026-05-28: Fixed in version 2.10.23 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45535 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45535?
- 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
A stored SQL injection vulnerability exists in DataEase versions prior to 2.10.23 within the SqlparserUtils.handleVariableDefaultValue() method. The root cause is the use of String.replace() to insert user-controlled 'defaultValue' entries into SQL templates without proper escaping or parameterization. An attacker with low-privileged access (permissions to create or edit datasets) can craft a malicious payload in the dataset variables. When any user with read access subsequently views the dataset, the injected SQL is executed. This can be exploited via error-based or time-based blind SQL injection to extract sensitive data from the backend database, including user hashes and system credentials. The issue is resolved in version 2.10.23 by implementing proper input neutralization.
Affected products
- DataEase DataEase < 2.10.23
Timeline
- 2026-05-28: patched: Fixed in version 2.10.23
- 2026-07-15: disclosed: Public advisory and CVE assignment