TYPO3CMS
CVE-2024-55922
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 · uneditedTYPO3 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 “Form Framework Module” allows attackers to manipulate or delete persisted form definitions. 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. There are no known workarounds for this vulnerability.
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 confidenceTYPO3 contains a CSRF vulnerability in its Form Framework Module where state-changing actions incorrectly accept HTTP GET requests instead of enforcing proper HTTP methods. Combined with disabled referrer enforcement (security.backend.enforceReferrer) and lax/none cookie SameSite settings, attackers can manipulate or delete persisted form definitions by tricking authenticated backend users into visiting malicious URLs.
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
>= 10.0.0, < 10.4.48>= 11.0.0, < 11.5.42>= 12.0.0, < 12.4.25>= 13.0.0, < 13.4.3CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed TYPO3 versionOpen the TYPO3 backend, go to 'About' module to view the version. Or via CLI: composer show typo3/cms-core 2>/dev/null | grep -i version, or check the file typo3/sysext/core/Classes/Information/Typo3Version.phpAffected if The installed version falls within any of these ranges: 10.0.0 to <10.4.48, 11.0.0 to <11.5.42, 12.0.0 to <12.4.25, or 13.0.0 to <13.4.3
-
Verify security.backend.enforceReferrer settingInspect the TYPO3 configuration file typo3conf/LocalConfiguration.php (or AdditionalConfiguration.php) and look for $GLOBALS['TYPO3_CONF_VARS']['BE']['security']['backendEnforceReferrer']Affected if The value is set to 0 (false) or the setting is absent (defaults may vary by version)
-
Check cookie SameSite configurationInspect typo3conf/LocalConfiguration.php and look for $GLOBALS['TYPO3_CONF_VARS']['BE']['cookieSameSite'] or $GLOBALS['TYPO3_CONF_VARS']['FE']['cookieSameSite']Affected if The value is set to 'none' or 'lax', which allows cookies to be sent in cross-site requests
You are affected if your TYPO3 version is within the vulnerable ranges AND security.backend.enforceReferrer is disabled AND cookie SameSite is set to none or lax, making CSRF attacks possible via GET requests to the Form Framework Module.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.4.4811.5.4212.4.25
Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, or 13.4.3 LTS. Ensure security.backend.enforceReferrer is enabled and review BE/cookieSameSite configuration.
TYPO3 11.5.42 LTS (ELTS), 12.4.25 LTS, or 13.4.3 LTS depending on current branch
- 1. Identify the currently installed TYPO3 version using the backend or command line (e.g., composer show typo3/cms-core or in TYPO3 admin tools > Install Tool > About)
- 2. For TYPO3 11.x: Upgrade to version 11.5.42 LTS (ELTS) by running: composer require typo3/cms-core:^11.5.42
- 3. For TYPO3 12.x: Upgrade to version 12.4.25 LTS by running: composer require typo3/cms-core:^12.4.25
- 4. For TYPO3 13.x: Upgrade to version 13.4.3 LTS by running: composer require typo3/cms-core:^13.4.3
- 5. Clear all caches after upgrade: rm -rf var/cache/* (or use Install Tool > Clear Caches)
- 6. Verify the upgrade was successful by checking the TYPO3 version in the backend
- 7. Test that the Form Framework Module functionality works correctly
- 8. Note: TYPO3 10.x is end-of-life and not receiving security fixes; migrate to a supported branch (11.x, 12.x, or 13.x)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in TYPO3
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-55922 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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