CVE-2025-58748: Dataease H2 data source JDBC URL validation bypass leads to remote code execution
Dataease is an open source data analytics and visualization platform. In Dataease versions up to 2.10.12 the H2 data source implementation (H2.java) does not verify that a provided JDBC URL starts with jdbc:h2. This lack of validation allows a crafted JDBC configuration that substitutes the Amazon Redshift driver and leverages the socketFactory and socketFactoryArg parameters to invoke org.springframework.context.support.FileSystemXmlApplicationContext or ClassPathXmlApplicationContext with an attacker‑controlled remote XML resource, resulting in remote code execution. Versions up to and including 2.10.12 are affected. The issue is fixed in version 2.10.13. Updating to version 2.10.13 or later is the recommended remediation. No known workarounds exist.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-58748?
CVE-2025-58748 has been assessed as a medium severity vulnerability due to potential data exposure risks.
How do I fix CVE-2025-58748?
To fix CVE-2025-58748, upgrade Dataease to version 2.10.13 or later, which includes the necessary validation for JDBC URLs.
What impact does CVE-2025-58748 have on Dataease?
CVE-2025-58748 may expose sensitive data due to improper validation of JDBC URLs in vulnerable versions of Dataease.
Which versions of Dataease are affected by CVE-2025-58748?
CVE-2025-58748 affects all versions of Dataease up to and including 2.10.12.
Is there a workaround for CVE-2025-58748 before applying the fix?
A temporary workaround for CVE-2025-58748 is to review and restrict JDBC URL configurations until the update can be applied.