DataEase up to 2.10.27/3.1.0 Chart Data ExtWhere2Str.java ExtWhere2Str.extWhere2sqlOjb operator sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in DataEase up to 2.10.27/3.1.0. Affected by this vulnerability is the function ExtWhere2Str.extWhere2sqlOjb of the file engine/trans/ExtWhere2Str.java of the component Chart Data Handler. Performing a manipulation of the argument operator results in sql injection. This vulnerability is cataloged as CVE-2026-123990. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is advisable to upgrade the affected component. The vendor confirms: "The fix validates the complete compound operator and uses fixed AND / OR keywords instead of concatenating user-controlled logic into SQL."

Detailsinfo

A vulnerability was found in DataEase up to 2.10.27/3.1.0. It has been classified as critical. This affects the function ExtWhere2Str.extWhere2sqlOjb of the file engine/trans/ExtWhere2Str.java of the component Chart Data Handler. The manipulation of the argument operator with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. This is going to have an impact on confidentiality, integrity, and availability.

This vulnerability is uniquely identified as CVE-2026-123990. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

It is declared as proof-of-concept. The vendor confirms: "The fix validates the complete compound operator and uses fixed AND / OR keywords instead of concatenating user-controlled logic into SQL."

Upgrading to version 3.2.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• DataEase

Version

• 2.10.0
• 2.10.1
• 2.10.2
• 2.10.3
• 2.10.4
• 2.10.5
• 2.10.6
• 2.10.7
• 2.10.8
• 2.10.9
• 2.10.10
• 2.10.11
• 2.10.12
• 2.10.13
• 2.10.14
• 2.10.15
• 2.10.16
• 2.10.17
• 2.10.18
• 2.10.19
• 2.10.20
• 2.10.21
• 2.10.22
• 2.10.23
• 2.10.24
• 2.10.25
• 2.10.26
• 2.10.27
• 3.0
• 3.1.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #1035483: FIT2CLOUD DataEase (open-source BI platform; vulnerable classes in the in-repo `core/core-backend` module bundled into the community distribution) 2.x <= 2.10.26 and 3.x <= 3.0.0 (the operator-logic concatenation is byte-identical in the `v2.10.26` and `v (by lucasg2g)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion