dbcve.org
TYPO3CMS

CVE-2024-22188

HIGH · 7.2 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 8.7.57 / 9.5.46 or later.
See remediation →
78/100
Remediation priority · High
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
TYPO3 before 13.0.1 allows an authenticated admin user (with system maintainer privileges) to execute arbitrary shell commands (with the privileges of the web server) via a command injection vulnerability in form fields of the Install Tool. The fixed versions are 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, and 13.0.1.

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

TYPO3 before 13.0.1 contains a command injection vulnerability in the Install Tool form fields, allowing authenticated administrators with system maintainer privileges to execute arbitrary shell commands with web server privileges.

MitigationUpdate TYPO3 to one of the fixed versions (8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, or 13.0.1). Restrict Install Tool access to only necessary personnel and monitor for unauthorized access.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TYPO3CMS
Affected:>= 8.0.0, < 8.7.57>= 9.0.0, < 9.5.46>= 10.0.0, < 10.4.43>= 11.0.0, < 11.5.35>= 12.0.0, < 12.4.11= 13.0.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 TYPO3 version
    Check the TYPO3 version by viewing the composer.json file in the project root, or check the TYPO3 backend under Admin Tools > About > Installed Versions, or inspect the Version.php file in typo3/sysext/core/Classes/
    Affected if The installed version falls within any of these ranges: >= 8.0.0 and < 8.7.57; >= 9.0.0 and < 9.5.46; >= 10.0.0 and < 10.4.43; >= 11.0.0 and < 11.5.35; >= 12.0.0 and < 12.4.11; or equals 13.0.0
  2. Verify Install Tool access
    Check if the TYPO3 Install Tool is accessible at /typo3/install or /install by attempting to access it or by reviewing web server configuration for any allow/deny rules
    Affected if The Install Tool is accessible from the network without proper restrictions
  3. Identify system maintainer accounts
    Query the be_users table in the TYPO3 database for records where admin = 1 and (be_users.tx_extbase_type = 'Tx_Extbase_Domain_Model_Administrator' OR the user has system maintainer privileges assigned), or check the Install Tool User Authentication section
    Affected if There are administrator accounts with system maintainer privileges that could access the vulnerable Install Tool form fields

You are affected if your TYPO3 installation version is within the affected ranges AND the Install Tool is accessible to authenticated administrators with system maintainer privileges.

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
Upgrade available Upgrade to 8.7.57 / 9.5.46 / 10.4.43 or later
Fixed in 8.7.579.5.4610.4.43
Interim mitigation

Update TYPO3 to one of the fixed versions (8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, or 13.0.1). Restrict Install Tool access to only necessary personnel and monitor for unauthorized access.

Recommended fix High confidence

Upgrade to the latest patch release in your supported branch: 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, or ideally the latest LTS (12.4.11 LTS or 13.0.1)

  1. Create a complete backup of the database and all site files
  2. Take the site offline or enable maintenance mode
  3. Review the TYPO3 upgrade guide for your current version path (refer to typo3.org/documentation/upgrade)
  4. Update TYPO3 core using Composer: composer require typo3/cms-core:^10.4.43 (or appropriate version for your branch)
  5. Run the database comparison and migration tool via Install Tool or command line (typo3cms database:compare)
  6. Clear all caches (typo3cms cache:flush)
  7. Verify the upgrade was successful by checking the TYPO3 version in the Install Tool or Admin panel
  8. Test critical site functionality including frontend, backend, and any custom extensions
Caveat Major version upgrades (e.g., 9.x to 10.x, 11.x to 12.x) may require extension compatibility updates and configuration changes; review TYPO3 change logs for breaking changes in each major version

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

Fix this in TYPO3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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