Skip to main content
CVE-2024-55081VulnerabilityPublished Updated

CVE-2024-55081: chat2DB · n/a

Affects chat2DBSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubsummerxxoo/chat2DBpkg:github/summerxxoo/chat2DBOther threatsAffected
  • =0.3.5
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-55081, organizations should take immediate and specific actions beyond generic advice: 1) Apply any available patches or updates from Chat2DB vendors as soon as they are released. 2) If patches are not yet available, disable or restrict access to the /datagrip/upload endpoint, especially from untrusted networks. 3) Implement strict XML parser configurations to disable external entity processing (e.g., disable DTDs and external entities in XML libraries used by Chat2DB). 4) Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious XML payloads containing external entity references. 5) Conduct thorough input validation and sanitization on all XML inputs before processing. 6) Monitor logs and network traffic for unusual XML requests or error messages indicative of XXE exploitation attempts. 7) Segment and isolate systems running Chat2DB to limit lateral movement if compromise occurs. 8) Educate development and security teams about secure XML handling practices to prevent similar vulnerabilities. 9) Consider deploying runtime application self-protection (RASP) tools that can detect and block exploitation attempts in real time. These targeted measures will reduce the attack surface and help prevent exploitation until a permanent fix is applied.

Description

An XML External Entity (XXE) injection vulnerability in the component /datagrip/upload of Chat2DB v0.3.5 allows attackers to execute arbitrary code via supplying a crafted XML input.

References

Community reviews

Loading reviews…