CVE-2025-58748
Published: 15 September 2025
Summary
CVE-2025-58748 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Dataease Dataease. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 17.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).
Deeper analysis
Dataease is an open source data analytics and visualization platform whose H2 data source implementation in versions up to and including 2.10.12 fails to enforce that JDBC URLs begin with the jdbc:h2 prefix. The affected code resides in H2.java and permits an attacker-supplied JDBC configuration to substitute the Amazon Redshift driver while supplying socketFactory and socketFactoryArg parameters that reference Spring’s FileSystemXmlApplicationContext or ClassPathXmlApplicationContext classes. This deserialization flaw, tracked as CWE-502, enables loading of an arbitrary remote XML resource and yields remote code execution.
An authenticated user with the ability to configure a data source can supply the malicious JDBC string, causing the application to instantiate attacker-controlled Spring application contexts and execute arbitrary code on the server. The attack requires network access and low-privileged credentials but no user interaction, consistent with the CVSS 8.7 rating.
The project’s security advisory and the commit that introduced the fix both state that the vulnerability is resolved in Dataease 2.10.13; administrators are advised to upgrade to that release or later, as no workarounds are documented. The associated EPSS score has remained flat at 0.0161 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-29201
Vulnerability details
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Direct RCE via malicious JDBC config on public-facing Dataease instance (CWE-502 deserialization) matches T1190 Exploit Public-Facing Application.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly mandates validation of untrusted inputs like JDBC URLs to ensure they conform to expected formats such as 'jdbc:h2', preventing driver substitution and malicious XML loading.
Requires timely flaw remediation through patching, such as updating Dataease to version 2.10.13, to address the specific H2 validation vulnerability.
Verifies integrity of software components and dynamically loaded resources like Spring ApplicationContext XML to block or detect malicious code execution from deserialization.