Skip to main content
VulnerabilityPublished Updated

CVE-2024-22219: Terminalfour · XML External Entity (XXE)

Source CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 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 26 Oct 2026.

What to do

AI-suggested

  1. Restrict access to Terminalfour and XML JDBC management interfaces to trusted users only and enforce strong authentication mechanisms, including multi-factor authentication (MFA) where possible.
  2. Monitor and audit XML input handling features for unusual or malformed XML submissions that could indicate exploitation attempts.
  3. Implement network segmentation to limit the ability of compromised accounts to access critical internal resources, reducing SSRF attack impact.
  4. Disable or properly configure XML external entity processing in XML parsers used by Terminalfour and XML JDBC components, if configurable, to prevent XXE exploitation.
  5. Apply the principle of least privilege to user accounts with access to affected systems, minimizing the potential damage from compromised credentials.
  6. Stay alert for official patches or updates from the vendor and apply them promptly once available.
  7. Use Web Application Firewalls (WAFs) with rules designed to detect and block malicious XML payloads targeting XXE vulnerabilities.
  8. Conduct regular security assessments and penetration testing focusing on XML input handling and authentication controls in affected environments.

Description

XML External Entity (XXE) vulnerability in Terminalfour 8.0.0001 through 8.3.18 and XML JDBC versions up to 1.0.4 allows authenticated users to submit malicious XML via unspecified features which could lead to various actions such as accessing the underlying server, remote code execution (RCE), or performing Server-Side Request Forgery (SSRF) attacks.

References

Community reviews

Loading reviews…