What is the CVSS score of CVE-2025-49002?

CVE-2025-49002 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2025-49002?

Yes, a public proof-of-concept exploit is available for CVE-2025-49002. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-49002?

Within 24 hours: Identify all DataEase instances in your environment and document current versions. Within 7 days: Apply the vendor-released patch to all DataEase deployments; verify patch installation by confirming version change and testing authentication controls. Within 30 days: Conduct a security audit of DataEase access logs to identify any unauthorized access attempts during the vulnerability window.

Dataease CVE-2025-49002

Q: Which versions of Dataease are affected by CVE-2025-49002?

DataEase contains a critical authentication bypass vulnerability (CVSS 9.8) that allows unauthenticated attackers to circumvent security controls, potentially exposing all organizational data and…. A patch is available.

EUVD-2025-16788 CRITICAL

Authentication Bypass by Spoofing (CWE-290)

2025-06-03 security-advisories@github.com

Authentication Bypass Code Injection Dataease

9.8

CVSS 3.1 · GitHub Advisory

View

Vulnerability Assessment

Weakness	CWE CWE-290 OWASP Top 10:2025 A07:2025 - Authentication Failures ASVS 5.0 V6 - Authentication Anti-spoofing controls MITRE ATT&CK 1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	CVSS 9.8.
Exploit ScenarioDerived	Evade previous auth fix.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

Auth bypass in DataEase via CVE-2025-49001 patch evasion. PoC available.

Earlier versions of this analysis (1)

v1 Mar 14, 2026 - 17:04 CVSS 9.8

Patch bypass auth bypass in DataEase.

RemediationAI

Update.

Affected VersionsENISA

dataease < 2.10.10

Affected Packages

euvd dataease fix: 2.10.10

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-290.

Know when Dataease gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 05:55 EUVD-patch-fix

executive summary

Patch available

Apr 16, 2026 - 05:29 EUVD

2.10.10

PoC Detected

Jun 05, 2025 - 14:07 vuln.today

Public exploit code

CVE Published

Jun 03, 2025 - 21:15 nvd

CRITICAL 9.8

DescriptionGitHub Advisory

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. The vulnerability has been fixed in v2.10.10. No known workarounds are available.

Executive ViewAI

Why It Matters

DataEase contains a critical authentication bypass vulnerability (CVSS 9.8) that allows unauthenticated attackers to circumvent security controls, potentially exposing all organizational data and analytics capabilities. This vulnerability affects any organization deploying DataEase and requires immediate patching to prevent unauthorized access to sensitive business intelligence and data assets.

Business Impact: Severe

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.1%

Top 67% exploitable

Exploit

POC

Public exploit code exists

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS POC (1)

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Out-of-Cycle

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

Very High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +49

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Authentication Bypass CRITICAL

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.