TYPO3CMS
CVE-2024-55892
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. Applications that use `TYPO3\CMS\Core\Http\Uri` to parse externally provided URLs (e.g., via a query parameter) and validate the host of the parsed URL may be vulnerable to open redirect or SSRF attacks if the URL is used after passing the validation checks. Users are advised to update to TYPO3 versions 9.5.49 ELTS, 10.4.48 ELTS, 11.5.42 LTS, 12.4.25 LTS, 13.4.3 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 confidenceThe TYPO3\CMS\Core\Http\Uri class has a flaw where URL validation checks can pass but the parsed URL used afterward may still be vulnerable to open redirect or SSRF attacks. When applications parse externally provided URLs (e.g., from query parameters) and validate the host, the internal representation of the URL differs from what was validated, allowing malicious URLs to pass validation checks and then be exploited.
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
>= 9.0.0, < 9.5.49>= 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Determine installed TYPO3 versionCheck the composer.json file or the TYPO3 version file (e.g., vendor/typo3/cms/composer.json) for the exact version numberAffected if The installed version falls within the affected ranges: >= 9.0.0 and < 9.5.49; >= 10.0.0 and < 10.4.48; >= 11.0.0 and < 11.5.42; >= 12.0.0 and < 12.4.25; or >= 13.0.0 and < 13.4.3
-
Identify usage of TYPO3 Uri class with external inputSearch codebase for usage of \TYPO3\CMS\Core\Http\Uri where the URI is constructed from request parameters (e.g., $_GET, $_POST, or PSR-7 request query parameters)Affected if The Uri class is instantiated with untrusted input from query parameters, POST data, or user-controlled sources
-
Check for URL validation patterns that rely on Uri::getHost()Search for code that validates URLs by calling getHost() or similar methods on the Uri object after construction from external input, then uses the original Uri objectAffected if Code validates the host of a URL but then uses the Uri object for requests, redirects, or other operations where the parsed URL may differ from what was validated
-
Identify redirect or HTTP request usage with validated Uri objectsSearch for code that performs HTTP requests (using HTTP client, curl, file_get_contents) or redirects (header Location, forward) using Uri objects that were validated with external inputAffected if The application makes outgoing HTTP requests or redirects using Uri objects created from external input without additional validation after the fix versions
A system is affected if it runs a vulnerable TYPO3 version AND uses the Uri class to parse externally-provided URLs (e.g., from query parameters) for validation followed by redirects or HTTP requests.
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 · scoped9.5.4910.4.4811.5.42
Update TYPO3 to versions 9.5.49 ELTS, 10.4.48 ELTS, 11.5.42 LTS, 12.4.25 LTS, or 13.4.3. No workarounds exist; the fix must be applied through version update.
Upgrade to TYPO3 9.5.49 (ELTS), 10.4.48 (ELTS), 11.5.42 (LTS), 12.4.25 (LTS), or 13.4.3 depending on your current major version
- 1. Identify the currently installed TYPO3 version by checking the system environment or composer.json
- 2. Determine the appropriate target version based on your current major version branch (see upgrade_path)
- 3. Create a complete backup of the database, file system, and configuration files
- 4. Test the upgrade in a non-production/staging environment first
- 5. Update dependencies via Composer: run `composer require typo3/cms-core:^<target_version> --with-all-dependencies` (replace <target_version> with 9.5.49, 10.4.48, 11.5.42, 12.4.25, or 13.4.3 as appropriate)
- 6. Clear all caches by deleting the var/cache and var/tmp directories
- 7. Run the database migration scripts if any are required (typically via the Install Tool)
- 8. Verify the upgrade by checking the TYPO3 version in the Admin Tools > About module
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in TYPO3
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55892 — 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-55892 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