dbcve.org
TYPO3CMS

CVE-2022-36107

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to after 11.5.15 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 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. It has been discovered that the `FileDumpController` (backend and frontend context) is vulnerable to cross-site scripting when malicious files are displayed using this component. A valid backend user account is needed to exploit this vulnerability. Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem. 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
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:>= 7.0.0, <= 7.6.57>= 8.0.0, <= 8.7.47>= 9.0.0, <= 9.5.36>= 10.0.0, <= 10.4.31>= 11.0.0, <= 11.5.15

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 a release after 11.5.15
Vendor patch github.com →
Recommended fix High confidence

TYPO3 11.5.16 (or 10.4.32, 9.5.37 ELTS, 8.7.48 ELTS, or 7.6.58 ELTS depending on your branch)

  1. Backup the current TYPO3 database and file system before proceeding with the upgrade
  2. Review the TYPO3 upgrade guide for your current version at https://docs.typo3.org/
  3. Ensure PHP version compatibility matches the requirements of the target TYPO3 version
  4. Download TYPO3 version 11.5.16 (or your preferred fixed version: 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, or 10.4.32) from https://get.typo3.org/
  5. Replace the core files with the new version, preserving local configuration in typo3conf/
  6. Run the database migration tool via the Install Tool or CLI: composer install or php typo3/sysext/core/bin/typo3 database:updates
  7. Clear all caches after the upgrade via Install Tool or CLI: php typo3/sysext/core/bin/typo3 cache:flush
  8. Verify backend login and frontend rendering work correctly
Caveat Patch releases within the same major.minor branch typically have minimal breaking changes; however, always test in a staging environment before deploying to production

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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