Skip to content
Fencer Intel
medium 5.3

CVE-2024-30269 json

DataEase has database configuration information exposure vulnerability

published 2y ago modified 4mo ago also EUVD-2024-28190

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
15.9%
EPSS 15.9% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

DataEase, an open source data visualization and analysis tool, has a database configuration information exposure vulnerability prior to version 2.5.0. Visiting the `/de2api/engine/getEngine;.js` path via a browser reveals that the platform's database configuration is returned. The vulnerability has been fixed in v2.5.0. No known workarounds are available aside from upgrading.

Patch / fix

  • dataease dataease 2.5.0

Is CVE-2024-30269 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 Fencer

Timeline

  1. Published
  2. First public exploit (EDB-52128)

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

15.88% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • EDB-52128 DataEase 2.4.0 - Database Configuration Information Exposure webapps, 2025-04-06

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • dataease dataease

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

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.