dbcve.org
TYPO3CMS

CVE-2023-47127

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 8.7.55 / 9.5.44 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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 an open source PHP based web content management system released under the GNU GPL. In typo3 installations there are always at least two different sites. Eg. first.example.org and second.example.com. In affected versions a session cookie generated for the first site can be reused on the second site without requiring additional authentication. This vulnerability has been addressed in versions 8.7.55, 9.5.44, 10.4.41, 11.5.33, and 12.4.8. Users are advised to upgrade. 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

A detailed technical summary for this CVE is being prepared.

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.55>= 9.0.0, < 9.5.44>= 10.0.0, < 10.4.41>= 11.0.0, < 11.5.33>= 12.0.0, < 12.4.8

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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.55 / 9.5.44 / 10.4.41 or later
Fixed in 8.7.559.5.4410.4.41
Vendor patch github.com →
Recommended fix High confidence

Upgrade to 8.7.55, 9.5.44, 10.4.41, 11.5.33, or 12.4.8 depending on your current branch

  1. 1. Backup the TYPO3 installation and database before proceeding
  2. 2. Determine your current version branch (8.x, 9.x, 10.x, 11.x)
  3. 3. Upgrade to the corresponding fixed version: 8.7.55 for 8.x, 9.5.44 for 9.x, 10.4.41 for 10.x, 11.5.33 for 11.x, or 12.4.8 for 12.x
  4. 4. Run the database migration scripts if prompted by the upgrade process
  5. 5. Clear all caches (temp_CACHED_*, var/cache/*) after the upgrade
  6. 6. Verify the upgrade was successful by logging in and testing session behavior across multiple sites
Caveat Minor: Review deprecation warnings and breaking changes notes in the release announcements for each version, especially when jumping across major version branches

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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