TYPO3CMS
CVE-2024-55945
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 “DB Check Module” allows attackers to manipulate data through unauthorized actions. Users are advised to update to TYPO3 versions 11.5.42 ELTS which fixes the problem described. There are no known workarounds for this issue.
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 backend UI deep link functionality. The DB Check Module downstream component incorrectly accepts state-changing actions via HTTP GET requests without enforcing proper HTTP method restrictions, allowing attackers to manipulate data through unauthorized actions when victims interact with malicious URLs while having an active backend session.
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
>= 11.0.0, < 11.5.42CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 TYPO3 versionLocate the TYPO3 version file (composer.json in the project root, or the version constant in TYPO3\Core\Utility\GeneralUtility class). Compare the installed version number against the affected range: >= 11.0.0 and < 11.5.42.Affected if The installed version is 11.0.0 through 11.5.41 (inclusive)
-
Verify DB Check module is installedCheck for the DB Check module in the TYPO3 backend under 'System > DB Check', or inspect the available backend modules in the system extension configuration (typically in typo3conf/PackageStates.php or the ext_tables.sql of the system extension).Affected if The DB Check module is installed and accessible in the backend
-
Confirm backend access is possibleDetermine if the TYPO3 backend is reachable (check if /typo3/ or the configured backend path responds) and whether any backend user accounts exist with active sessions possible.Affected if The TYPO3 backend interface is accessible and user authentication is configured
-
Identify HTTP method configurationReview the TYPO3 configuration for the DB Check module actions. Inspect any custom or overridden controller code in the DB Check module that handles state-changing operations (typically found in sysext/beuser/Controller/ or related DB Check controllers). Look for action methods that respond to GET requests.Affected if The DB Check module controllers accept GET requests for actions that modify data (such as clearing caches, manipulating records, or triggering maintenance tasks)
You are affected if TYPO3 version is between 11.0.0 and 11.5.41 inclusive, the DB Check module is enabled, and the backend is accessible with GET-based state-changing actions permitted.
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 · scoped11.5.42
Update TYPO3 to version 11.5.42 ELTS which fixes the CSRF vulnerability and enforces proper HTTP method handling in affected components.
TYPO3 11.5.42 ELTS
- 1. Back up your TYPO3 installation, including the database and all files.
- 2. Ensure you have a complete backup before proceeding with the upgrade.
- 3. Update TYPO3 to version 11.5.42 ELTS using your preferred installation method (e.g., Composer, Extension Manager, or manual file replacement).
- 4. After upgrading, clear all caches to ensure the new version's files are properly loaded.
- 5. Verify that the backend is accessible and all extensions are functioning correctly.
- 6. Test critical backend functionality, especially the DB Check Module, to confirm the vulnerability is resolved.
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
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55945 — 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-55945 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