CVE-2025-49001 Dataease Authentication Bypass Vulnerability
Attackers can forge JWT tokens using any secret due to failed verification, allowing unauthorized access to the DataEase business intelligence platform.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-49001?
CVE-2025-49001 is a high-severity authentication bypass vulnerability in Dataease Dataease, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2025-49001?
It affects 1 product.
Products include Dataease Dataease.
How do I fix CVE-2025-49001?
No fix has been published for CVE-2025-49001 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-49001 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49001 exists.
Public exploit code: 1 Nuclei template.
Other vulnerabilities in Dataease Dataease
- CVE-2024-57707 Code injection in n/a
- CVE-2024-46997 DataEase's H2 datasource has a remote command execution risk
- CVE-2023-33963 DataEase data source has deserialization vulnerability
- CVE-2023-28437 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed
- CVE-2022-39312 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability
Sources
Also known as GHSA-xx2m-gmwg-mf3r.