Chaindataease
dataease: fix bypasses (2024–2025)
3 CVEs over 3 generations, 18 Dec 2024 to 3 Jun 2025.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2024-5595318 Dec 2024 First in the chain
- CVE-2025-2710313 Mar 2025 bypassed the fix for CVE-2024-55953
- CVE-2025-489983 Jun 2025 bypassed the fix for CVE-2025-27103
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2024-55953 | 18 Dec 2024 | Dataease Mysql JDBC Connection Parameters Not Verified Leads to Deserialization and Arbitrary File Read Vulnerability | First in chain | 18.8 |
| CVE-2025-27103 | 13 Mar 2025 | Dataease Mysql JDBC Connection Parameters Not Being Verified Leads to Arbitrary File Read Vulnerability | CVE-2024-55953 · bypassed the fix · High | 13.1 |
| CVE-2025-48998 | 3 Jun 2025 | Dataease MYSQL JDBC File Reading Vulnerability | CVE-2025-27103 · bypassed the fix · High | 14.0 |