dbcve.org
TYPO3CMS

CVE-2024-55921

HIGH · 8.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 10.4.48 / 11.5.42 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions: The user opens a malicious link, such as one sent via email. The user visits a compromised or manipulated website while the following settings are misconfigured: 1. `security.backend.enforceReferrer` feature is disabled, 2. `BE/cookieSameSite` configuration is set to lax or none. The vulnerability in the affected downstream component “Extension Manager Module” allows attackers to retrieve and install 3rd party extensions from the TYPO3 Extension Repository - which can lead to remote code execution in the worst case. Users are advised to update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS which fix the problem described.

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 contains a CSRF vulnerability in its backend deep link functionality where state-changing actions (specifically in the Extension Manager Module) incorrectly accept HTTP GET requests. Combined with misconfigured security settings (disabled referrer enforcement or lax cookie SameSite), attackers can trick authenticated backend users into installing malicious extensions, potentially achieving remote code execution.

MitigationUpdate to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, or 13.4.3 LTS. Additionally, ensure security.backend.enforceReferrer is enabled and BE/cookieSameSite is set to strict.

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:>= 10.0.0, < 10.4.48>= 11.0.0, < 11.5.42>= 12.0.0, < 12.4.25>= 13.0.0, < 13.4.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check installed TYPO3 version
    Locate the file 'typo3/sysext/core/Classes/Information/Typo3Version.php' or check the TYPO3 backend under Admin Tools > About > Version. Compare the installed version number against the affected ranges: 10.0.0 to 10.4.47, 11.0.0 to 11.5.41, 12.0.0 to 12.4.24, or 13.0.0 to 13.4.2.
    Affected if The installed version falls within any of these ranges and the Extension Manager module is accessible to backend users.
  2. Verify backend referrer enforcement is disabled
    Inspect the TYPO3 configuration file 'typo3conf/LocalConfiguration.php' or check the file 'typo3conf/AdditionalConfiguration.php'. Look for the key 'BE/security/backend/enforceReferrer' and note its boolean value.
    Affected if The value is set to false, which allows the CSRF attack to succeed.
  3. Check cookie SameSite setting
    In the same configuration files ('typo3conf/LocalConfiguration.php' or 'typo3conf/AdditionalConfiguration.php'), locate 'BE/cookieSameSite' and note its value.
    Affected if The value is set to 'lax' or is missing/empty, which weakens CSRF protection for the backend cookies.
  4. Confirm Extension Manager accessibility
    Log into the TYPO3 backend and navigate to the Admin Tools > Extensions module. Verify whether the current user has permission to access this module.
    Affected if The authenticated user can access the Extension Manager and perform installations or updates.

You are affected if your TYPO3 version is in the vulnerable range AND the Extension Manager is accessible AND either referrer enforcement is disabled or cookie SameSite is set to lax.

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 10.4.48 / 11.5.42 / 12.4.25 or later
Fixed in 10.4.4811.5.4212.4.25
Interim mitigation

Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, or 13.4.3 LTS. Additionally, ensure security.backend.enforceReferrer is enabled and BE/cookieSameSite is set to strict.

Recommended fix High confidence

Upgrade to TYPO3 10.4.48 (for v10), 11.5.42 ELTS (for v11), 12.4.25 LTS (for v12), or 13.4.3 LTS (for v13)

  1. 1. Take a complete backup of the TYPO3 database and all files
  2. 2. Verify that your current PHP version is compatible with the target TYPO3 version (PHP 7.4+ for v10/v11, PHP 8.1+ for v12/v13)
  3. 3. Check all installed extensions for compatibility with the target TYPO3 version
  4. 4. Update TYPO3 core to version 10.4.48 if running 10.x, 11.5.42 if running 11.x, 12.4.25 if running 12.x, or 13.4.3 if running 13.x
  5. 5. Clear all caches after the upgrade (delete typo3temp and var/cache directories)
  6. 6. Log in to the backend and verify the installation is working correctly
  7. 7. Ensure security.backend.enforceReferrer is enabled (default) in Install Tool > All Configuration
  8. 8. Verify BE/cookieSameSite is set to strict (not lax or none) in Install Tool > All Configuration
Caveat Review extension compatibility before upgrading; major version jumps may require code adjustments

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

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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