dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2024-22218

HIGH · 8.8 CVSS v3.1 Published 2024-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an XXE vulnerability in Terminalfour CMS and XML JDBC components where authenticated users can submit malicious XML containing external entity references. The vulnerability stems from improper configuration of XML parsers allowing external entity resolution, which can be leveraged to read local files, perform SSRF, or achieve RCE.

MitigationDisable external entity processing and DTD processing in all XML parsers used by the application, or upgrade to patched versions of Terminalfour (8.3.19+) and XML JDBC (1.0.5+). Input validation for XML content should also be implemented.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Terminalfour CMS version
    Locate the version information in the administration interface under System Information or check version files in the installation directory. Compare the installed version number against the affected range (versions prior to 8.3.19).
    Affected if The installed version is earlier than 8.3.19 and the application processes XML input.
  2. Identify XML JDBC component version
    Check the XML JDBC component version in the application dependencies, libraries directory, or administration panel. Compare against the affected range (versions prior to 1.0.5).
    Affected if The XML JDBC component version is earlier than 1.0.5 and the component handles XML content.
  3. Verify XML processing functionality is in use
    Identify if the application accepts XML uploads, parses XML content from user input, or uses XML JDBC for data import/export. Check application modules that handle XML-based content or data feeds.
    Affected if XML processing features are enabled and accessible to authenticated users.
  4. Inspect XML parser configuration
    Examine the XML parser configuration files or settings within Terminalfour that control entity resolution. Look for parser settings that enable external entity processing, DTD processing, or external document type definition access.
    Affected if XML parsers are configured to allow external entity resolution or DTD processing.
  5. Review user permissions for XML input
    Check which user roles or groups have permission to submit XML content, use XML JDBC functionality, or access XML-based import features.
    Affected if Authenticated users have privileges to submit or process XML content.

A user is affected if they run Terminalfour CMS or XML JDBC component versions prior to the patched releases AND the application has XML processing enabled for authenticated users with parser configurations allowing external entity resolution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable external entity processing and DTD processing in all XML parsers used by the application, or upgrade to patched versions of Terminalfour (8.3.19+) and XML JDBC (1.0.5+). Input validation for XML content should also be implemented.

Recommended fix Moderate confidence

Terminalfour version 8.3.19 or later (latest stable release)

  1. 1. Identify the current Terminalfour version in use (check About or System Information section in admin panel)
  2. 2. If running version 8.0.0001 through 8.3.18, plan for upgrade to latest stable release
  3. 3. If using XML JDBC version 1.0.4 or earlier, verify if a newer XML JDBC version is available
  4. 4. Schedule maintenance window for upgrade procedure
  5. 5. Perform full backup of database and application files before upgrading
  6. 6. Upgrade Terminalfour to the latest available version beyond 8.3.18
  7. 7. Verify XML parser configuration disables external entity processing if available
  8. 8. Test XML-based functionality post-upgrade to confirm proper operation
Caveat Review release notes for version 8.3.19+ to check for configuration or feature changes that may require adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22218 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22218 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data