dbcve.org
DataeaseApplication

CVE-2025-53006

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

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 business intelligence and data visualization tool. Prior to version 2.10.11, in both PostgreSQL and Redshift, apart from parameters like "socketfactory" and "socketfactoryarg", there are also "sslfactory" and "sslfactoryarg" with similar functionality. The difference lies in that "sslfactory" and related parameters need to be triggered after establishing the connection. Other similar parameters include "sslhostnameverifier", "sslpasswordcallback", and "authenticationPluginClassName". This issue has been patched in 2.10.11.

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 prior to 2.10.11 contain a critical JDBC parameter injection vulnerability affecting PostgreSQL and Redshift database connections. The 'sslfactory', 'sslfactoryarg', 'sslhostnameverifier', 'sslpasswordcallback', and 'authenticationPluginClassName' parameters can be manipulated (similar to the previously documented socketfactory parameters) to achieve arbitrary code execution by loading malicious custom SSL factories or authentication plugins after the database connection is established. This enables unauthenticated remote code execution with CVSS 9.8.

MitigationUpgrade DataEase to version 2.10.1 or later immediately. If immediate upgrade is not feasible, restrict administrative access to database connection configuration and implement network segmentation to limit exposure.

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.11

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. Identify installed Dataease version
    Check the Dataease application version through the admin interface (usually in Settings > About) or check the version file in the Dataease installation directory
    Affected if The installed version is lower than 2.10.11
  2. Check for PostgreSQL database connections
    Review all configured database connections in Dataease under Data Sources or Connection settings. Look for connections using PostgreSQL JDBC driver
    Affected if PostgreSQL connections exist and users can configure or modify connection parameters
  3. Check for Redshift database connections
    Review all configured database connections in Dataease under Data Sources or Connection settings. Look for connections using Amazon Redshift JDBC driver
    Affected if Redshift connections exist and users can configure or modify connection parameters
  4. Inspect connection parameter inputs
    Examine the database connection creation/editing forms in Dataease. Check if there are fields that allow arbitrary JDBC parameters (such as sslfactory, sslfactoryarg, sslhostnameverifier, sslpasswordcallback, or authenticationPluginClassName)
    Affected if Users can specify custom JDBC parameters in connection configuration forms

You are affected if Dataease version is below 2.10.11 AND PostgreSQL or Redshift connections can be configured with custom JDBC parameters.

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.11 or later
Fixed in 2.10.11
Interim mitigation

Upgrade DataEase to version 2.10.1 or later immediately. If immediate upgrade is not feasible, restrict administrative access to database connection configuration and implement network segmentation to limit exposure.

Recommended fix High confidence

2.10.11

  1. 1. Back up your current Dataease installation and database before proceeding with any upgrade.
  2. 2. Download Dataease version 2.10.11 or later from the official GitHub releases page (github.com).
  3. 3. Stop the running Dataease service to prevent data inconsistency during upgrade.
  4. 4. Follow the official Dataease upgrade documentation for your deployment method (Docker, Kubernetes, or direct installation).
  5. 5. Start the upgraded Dataease service and verify it runs successfully.
  6. 6. Test database connections for PostgreSQL and Redshift data sources to confirm the vulnerability is mitigated.
  7. 7. Review user access permissions and data source configurations after upgrade.

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

Fix this in Dataease Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53006 — 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-53006 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