dbcve.org
DataeaseApplication

CVE-2025-58748

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 2.10.13 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Dataease versions up to 2.10.12 have a critical vulnerability in the H2 data source implementation where H2.java does not validate that JDBC URLs start with 'jdbc:h2'. Attackers can craft a malicious JDBC configuration that substitutes the Amazon Redshift driver and uses socketFactory/socketFactoryArg parameters to trigger Spring's FileSystemXmlApplicationContext or ClassPathXmlApplicationContext with a remote XML file, achieving remote code execution.

MitigationImmediately upgrade Dataease to version 2.10.13 or later to apply the fix that adds proper JDBC URL validation. No workarounds are available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DataeaseApplication
Affected:< 2.10.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Dataease version
    Locate the Dataease installation and identify the installed version number (typically found in the application metadata, about page, or installation directory). Compare it to the affected range: versions < 2.10.13 are vulnerable.
    Affected if The installed Dataease version is lower than 2.10.13
  2. Verify H2 data source is enabled
    Check if the H2 database feature is configured or active in the Dataease instance. Look for data source configuration files, database connection settings, or H2-related modules.
    Affected if H2 data source functionality is enabled or configured in the environment
  3. Inspect JDBC URL configuration for H2
    Examine the H2.java configuration file or data source settings to determine if JDBC URL validation is performed. Look for whether the code validates that JDBC URLs start with 'jdbc:h2' before use.
    Affected if The H2.java implementation lacks proper JDBC URL validation (URLs are not required to start with 'jdbc:h2')
  4. Check for custom JDBC driver configurations
    Review any custom data source configurations where users can specify JDBC connection strings. Look for parameters like socketFactory or socketFactoryArg in JDBC connection strings.
    Affected if Custom JDBC URL parameters (particularly socketFactory/socketFactoryArg) can be injected into the H2 data source configuration

Your environment is affected if you are running Dataease version lower than 2.10.13 AND the H2 data source feature is enabled, allowing JDBC URLs that do not start with 'jdbc:h2' to be configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.13 or later
Fixed in 2.10.13
Vendor patch github.com →
Interim mitigation

Immediately upgrade Dataease to version 2.10.13 or later to apply the fix that adds proper JDBC URL validation. No workarounds are available.

Recommended fix High confidence

Dataease 2.10.13

  1. 1. Back up your current Dataease installation and database
  2. 2. Stop the Dataease service
  3. 3. Upgrade to Dataease version 2.10.13 or later
  4. 4. Start the Dataease service and verify it is running correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dataease Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58748 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data