CVE-2025-49001 in the critical feed json
Dataease Authentication Bypass Vulnerability
published last yr. modified 4mo ago also EUVD-2025-16789
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 22.0%
- EPSS 22.0% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- dataease dataease 2.10.10
- dataease_project dataease 2.10.10
Is CVE-2025-49001 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
22.00% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template DataEase < 2.10.10 - JWT Authentication Bypass nuclei detection template
- github.com https://github.com/dataease/dataease/security/advisories/GHSA-xx2m-gmwg-mf3r referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.7 | 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 |
| CNA | 4.0 | 7.7 | 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- dataease dataease
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/dataease/dataease/security/advisories/GHSA-xx2m-gmwg-mf3r
exploit, broken-link
Sources
- CVE List CVE-2025-49001
- NVD CVE-2025-49001
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.