CVE-2026-53730

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, the /de2api/datasetData/previewSql endpoint lacks the mandatory @DePermit permission validation annotation, allowing any authenticated user to specify datasourceId=-1, access the built-in engine database, execute arbitrary SQL statements, and read sensitive core data. This issue is fixed in version 2.10.24.

CVSS v3
8.7
EG Score
8.7(medium)
EPSS
14.4%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Unauthorized Access to Engine Database via previewSql Endpoint · Advisory · dataease/dataease · GitHub

Affected: v2.10.24.

https://github.com/dataease/dataease/security/advisories/GHSA-2jmq-vffm-4qmj
github_commit

commit 7b47af38b8fa (dataease/dataease)

Fix landed in dataease/dataease commit 7b47af38b8fa — awaiting tagged release

https://github.com/dataease/dataease/commit/7b47af38b8fa017c9eecb00a4a49264663189e7b

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 21:32 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 10:13 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 22:52 UTCEG score recompute
  8. 2026-07-14 11:33 UTCEG score recompute
  9. 2026-07-14 00:14 UTCEG score recompute
  10. 2026-07-13 22:31 UTCEPSS rescore
  11. 2026-07-13 12:55 UTCEG score recompute
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 01:36 UTCEG score recompute
  15. 2026-07-12 14:17 UTCEG score recompute
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-12 02:58 UTCEG score recompute
  18. 2026-07-11 15:39 UTCEG score recompute
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-11 04:20 UTCEG score recompute
  22. 2026-07-10 17:01 UTCEG score recompute
  23. 2026-07-10 05:40 UTCEG score recompute
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 8 more
  1. 2026-07-09 18:21 UTCEG score recompute
  2. 2026-07-09 07:01 UTCEG score recompute
  3. 2026-07-08 19:41 UTCEG score recompute
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-08 08:21 UTCEG score recompute
  7. 2026-07-07 21:03 UTCEG score recompute
  8. 2026-07-07 21:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53730?
CVE-2026-53730 is a high vulnerability published on July 7, 2026. DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, the /de2api/datasetData/previewSql endpoint lacks the mandatory @DePermit permission validation annotation, allowing any authenticated user to specify datasourceId=-1, access the built-in engine database, execute…
When was CVE-2026-53730 disclosed?
CVE-2026-53730 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53730 actively exploited?
CVE-2026-53730 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53730?
CVE-2026-53730 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-53730?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53730, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53730

Explore →

Is Your Infrastructure Affected by CVE-2026-53730?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs