Cyber Resilience

CVE-2025-49002

HighPublic PoC

Published: 03 June 2025

Published
03 June 2025
Modified
05 June 2025
KEV Added
Patch
CVSS Score v4 8.2 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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
EPSS Score 0.2617 96.4th percentile
Risk Priority 32 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2025-49002 is a high-severity Authentication Bypass by Spoofing (CWE-290) vulnerability in Dataease Dataease. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 3.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis

DataEase, an open source business intelligence and data visualization tool, contains a bypass of the prior patch for CVE-2025-32966 in all versions before 2.10.10. The flaw stems from case-insensitive handling of the blocked INIT and RUNSCRIPT keywords, allowing the original restriction to be evaded and resulting in a vulnerability rated at CVSS 8.2 with CWE-290 characteristics.

An unauthenticated remote attacker can supply specially crafted input that bypasses the keyword filter, achieving high impact on confidentiality, integrity, and availability of the affected DataEase instance. The attack requires no user interaction or privileges and can be performed over the network despite the high attack complexity noted in the scoring vector.

The GitHub Security Advisories GHSA-999m-jv2p-5h34 and GHSA-h7hj-4j78-cvc7 state that the issue is resolved in DataEase 2.10.10 and that no workarounds are available. The associated EPSS score has remained flat at 0.2617 with no material increase after disclosure.

EU & UK References

Vulnerability details

DataEase is an open source business intelligence and data visualization tool. Versions prior to version 2.10.10 have a flaw in the patch for CVE-2025-32966 that allow the patch to be bypassed through case insensitivity because INIT and RUNSCRIPT are prohibited.…

more

The vulnerability has been fixed in v2.10.10. No known workarounds are available.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

CVE-2025-49002 allows unauthenticated remote code execution via a crafted JDBC URL in the datasource validation API, bypassing case-insensitive restrictions on H2 database INIT/RUNSCRIPT commands, exploiting a public-facing web application.

Affected Assets

dataease
dataease
≤ 2.10.10

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-290

Reveals spoofed logon attempts through unexpected previous logon timestamps upon legitimate login.

addresses: CWE-290

Training specifically addresses recognizing spoofed communications and phishing that enable authentication bypass.

addresses: CWE-290

Requiring verifiable identity evidence at appropriate assurance levels makes it substantially harder for attackers to successfully spoof or impersonate users to obtain accounts.

addresses: CWE-290

Unique device authentication makes successful spoofing of device identity substantially more difficult to achieve.

addresses: CWE-290

Unique identification of non-organizational users reduces the feasibility of authentication bypass by spoofing.

addresses: CWE-290

Unique identification and authentication of services before communications makes spoofing of service identities substantially harder.

addresses: CWE-290

Isolated trusted path ensures the user interacts only with genuine system components, preventing spoofing of authentication interfaces or prompts.

addresses: CWE-290

Directly counters DNS response spoofing by requiring cryptographic origin authentication artifacts from the authoritative source.

References