Quick answers
- Is CVE-2026-45320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45320 being exploited in the wild.
- How severe is CVE-2026-45320?
- 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-45320?
- 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-45320 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45320?
- 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 SQL injection vulnerability exists in DataEase's dashboard variable processing logic within the 'SqlparserUtils.transFilter()' method. When processing SQL variables (e.g., ${variable_name}), the application fails to sanitize input for operators other than 'in' or 'between' (such as '=', '!=', '<', '>', or 'like'), returning the raw user-provided string. This unsanitized value is then directly concatenated into the final SQL query via 'SubstitutedSql.replace()'. An authenticated attacker with dashboard viewing privileges can exploit this by sending a crafted POST request to the query endpoint containing SQL injection payloads in the filter values. This can result in unauthorized data extraction from any integrated data source, including MySQL, PostgreSQL, and Oracle. The vulnerability is addressed in version 2.10.23.
Affected products
- DataEase DataEase < 2.10.23
Timeline
- 2026-05-28: patched: Version 2.10.23 released
- 2026-07-15: disclosed: Public advisory published