dbcve.org
DataeaseApplication

CVE-2025-53005

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-01
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, there is a bypass vulnerability in Dataease's PostgreSQL Data Source JDBC Connection Parameters. The sslfactory and sslfactoryarg parameters could trigger a bypass vulnerability. This issue has been patched in version 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 bypass vulnerability in the PostgreSQL Data Source JDBC Connection Parameters. The sslfactory and sslfactoryarg parameters can be manipulated to bypass SSL/TLS security controls in database connections, allowing potential man-in-the-middle attacks or unauthorized data access.

MitigationUpgrade DataEase to version 2.10.11 or later to patch the vulnerability. Review and restrict permissions for users who can configure data source connections.

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. Check installed DataEase version
    Access the DataEase admin interface or check the deployed application version file (typically found in the installation directory or via the /api/system/info endpoint)
    Affected if The installed version is prior to 2.10.11 (e.g., 2.10.10, 2.10.0, 2.9.x, etc.)
  2. Identify configured PostgreSQL data sources
    Navigate to Data Source management in the DataEase admin panel and review the list of configured data sources, filtering for those using PostgreSQL as the database type
    Affected if There are PostgreSQL data sources configured and the DataEase version is vulnerable
  3. Inspect JDBC connection parameters for sslfactory
    For each PostgreSQL data source, examine the JDBC connection parameters field for the presence of the 'sslfactory' parameter (case-insensitive search)
    Affected if The sslfactory parameter is present in the JDBC connection string with custom values that could bypass SSL/TLS verification
  4. Inspect JDBC connection parameters for sslfactoryarg
    For each PostgreSQL data source, examine the JDBC connection parameters field for the presence of the 'sslfactoryarg' parameter
    Affected if The sslfactoryarg parameter is present in the JDBC connection string, as it can be manipulated to bypass SSL/TLS controls

A user is affected if their DataEase installation version is prior to 2.10.11 AND they have PostgreSQL data sources configured with sslfactory or sslfactoryarg parameters in the JDBC connection settings.

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.11 or later to patch the vulnerability. Review and restrict permissions for users who can configure data source connections.

Recommended fix High confidence

2.10.11

  1. Upgrade Dataease to version 2.10.11 or later to remediate the PostgreSQL JDBC connection parameter bypass vulnerability
  2. After upgrading, verify that the sslfactory and sslfactoryarg parameters are properly restricted or filtered in the PostgreSQL data source configuration
  3. Test that PostgreSQL data sources can still connect successfully after the upgrade

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

Fix this in Dataease Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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