Cyber Resilience

CVE-2025-53006

Dataease ≤ 2.10.11

Public PoC
Published
02 July 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 8.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/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.0054 43th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2025-53006 is a high-severity Improper Neutralization of Substitution Characters (CWE-153) vulnerability in Dataease Dataease. Its CVSS base score is 8.9 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.11, in both PostgreSQL and Redshift, apart from parameters like "socketfactory" and "socketfactoryarg", there are also "sslfactory" and "sslfactoryarg" with similar functionality. The difference lies in…

more

that "sslfactory" and related parameters need to be triggered after establishing the connection. Other similar parameters include "sslhostnameverifier", "sslpasswordcallback", and "authenticationPluginClassName". This issue has been patched in 2.10.11.

CWE(s)
CWE-153

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
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.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-53004Same product: Dataease Dataease
CVE-2025-49003Same product: Dataease Dataease
CVE-2025-53005Same product: Dataease Dataease
CVE-2023-25807Same product: Dataease Dataease
CVE-2024-56511Same product: Dataease Dataease
CVE-2026-33207Same product: Dataease Dataease
CVE-2025-62421Same product: Dataease Dataease
CVE-2025-62422Same product: Dataease Dataease
CVE-2023-37258Same product: Dataease Dataease
CVE-2026-33082Same product: Dataease Dataease

Affected Assets

dataease
dataease
≤ 2.10.11

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.9
  • V1.2.10

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly requires neutralizing or rejecting dangerous substitution characters before they reach a downstream interpreter.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization of substitution characters.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect substitution-character flaws but does not itself implement neutralization.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and sanitization that directly prevents substitution-character injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing special elements before downstream processing.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper neutralization of substitution characters in all input handling.

References