Skip to main content
CVE-2025-49001VulnerabilityPublished

CVE-2025-49001: dataease · Improper Authentication

Affects dataeaseSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 21% EPSS · CVSS 7.7 High : upgrade to 2.10.10 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
21.7% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.10.10
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade dataease/dataease to 2.10.10.

Affected software

ProductAffectedFixed in
GitHubdataease/dataeasepkg:github/dataease/dataeaseOther threatsAffected
  • <2.10.10
Fixed in
  • 2.10.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize upgrading DataEase installations to version 2.10.10 or later to remediate this vulnerability. In environments where immediate patching is not feasible, organizations should implement strict network segmentation and firewall rules to restrict access to DataEase servers, limiting exposure to trusted internal networks only. Employing Web Application Firewalls (WAFs) with custom rules to detect and block malformed or unauthorized JWT tokens can provide temporary protection. Monitoring authentication logs for unusual token usage patterns or failed verification attempts can help detect exploitation attempts early. Additionally, organizations should review and tighten access controls around DataEase instances, enforce strong authentication mechanisms at the perimeter, and conduct regular security audits to ensure no unauthorized access has occurred. Finally, educating administrators about the vulnerability and ensuring timely application of security updates is critical to maintaining a secure environment.

Description

DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.10, secret verification does not take effect successfully, so a user can use any secret to forge a JWT token. The vulnerability has been fixed in v2.10.10. No known workarounds are available.

References

Community reviews

Loading reviews…