Description
DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, ShareSecretManage uses a hardcoded default share link signature key, allowing an attacker who can obtain a passwordless share for a resource and user to use the known key link-pwd-fit2cloud to forge linkToken JWTs, bypass TokenFilter verification, and access backend resources as the share creator even if the original share has been revoked. This issue is fixed in version 2.10.24.
Published: 2026-07-07
Score: 8.3 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

DataEase’s ShareLink feature hardcodes the JWT signing secret "link-pwd-fit2cloud" in all releases before version 2.10.24. The likely attack vector is an attacker using an exposed passwordless share link to combine the known secret with a crafted payload, producing a valid linkToken that passes the TokenFilter validation. This permits the attacker to impersonate the original share creator and access protected backend resources, even if the share has been revoked. The flaw exemplifies hardcoded cryptographic material (CWE‑321) and use of default secrets (CWE‑798).

Affected Systems

All installations of the DataEase data visualization platform using the dataease product with a version older than 2.10.24 contain the flaw. Updating to version 2.10.24 or later removes the hardcoded signing key and eliminates the vulnerability.

Risk and Exploitability

The CVSS score of 8.3 indicates high severity, while the EPSS score of less than 1% suggests a low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. However, because an attacker only needs a passwordless share link—something that can be achieved through normal sharing or by discovering publicly exposed URLs—the potential impact remains significant. Without remediation, the ability to forge JWTs and bypass authentication would grant an attacker unauthorized backend access.

Generated by OpenCVE AI on July 31, 2026 at 14:12 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade DataEase to version 2.10.24 or newer to remove the hardcoded signing secret.
  • Disable or revoke all existing ShareLink URLs until the patch is applied.
  • Monitor backend authentication logs for anomalous linkToken usage and enforce stricter access controls as a temporary containment measure.

Generated by OpenCVE AI on July 31, 2026 at 14:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 08 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 07 Jul 2026 23:30:00 +0000

Type Values Removed Values Added
First Time appeared Dataease
Dataease dataease
Vendors & Products Dataease
Dataease dataease

Tue, 07 Jul 2026 21:00:00 +0000

Type Values Removed Values Added
Description DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, ShareSecretManage uses a hardcoded default share link signature key, allowing an attacker who can obtain a passwordless share for a resource and user to use the known key link-pwd-fit2cloud to forge linkToken JWTs, bypass TokenFilter verification, and access backend resources as the share creator even if the original share has been revoked. This issue is fixed in version 2.10.24.
Title DataEase: Hardcoded JWT Signing Secret in ShareLink
Weaknesses CWE-321
CWE-798
References
Metrics cvssV4_0

{'score': 8.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Dataease Dataease
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-08T13:37:38.831Z

Reserved: 2026-06-24T01:47:55.285Z

Link: CVE-2026-57172

cve-icon Vulnrichment

Updated: 2026-07-08T13:37:09.719Z

cve-icon NVD

Status : Deferred

Published: 2026-07-07T21:17:28.223

Modified: 2026-07-08T15:07:37.767

Link: CVE-2026-57172

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T14:15:03Z

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

  • CWE-798

    Use of Hard-coded Credentials