Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.0

Backend Same-Site Request Forgery in TYPO3 CMS

CVE-2020-11069GHSA-pqg8-crx9-g8m4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms-core 10.4.2, 9.5.17; typo3/cms 10.4.2, 9.5.17), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms-core

    Affected
    >= 9.0.0, < 9.5.17>= 10.0.0, < 10.4.2
    Fixed in
    9.5.17, 10.4.2

  • Packagist typo3/cms

    Affected
    >= 10.0.0, < 10.4.2>= 9.0.0, < 9.5.17
    Fixed in
    9.5.17, 10.4.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2020-11069: 0.74% estimated exploitation activity in the next 30 days; percentile 54.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Meta CVSS v3.1: AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C CWE-352 CWE-346 Problem It has been discovered that backend user interface and install tool are vulnerable to same-origin request forgery. A backend user can be tricked into interacting with a malicious resource an attacker previously managed to upload to the web server - scripts are then executed with the privileges of the victims' user session. In a worst case scenario new admin users can be created which can directly be used by an attacker. The vulnerability is basically a cross-site request forgery (CSRF) triggered by a cross-site scripting vulnerability (XSS) - but happens on the same target host - thus, it’s actually a same-origin request forgery. Malicious payload such as HTML containing JavaScript might be provided by either an authenticated backend user or by a non-authenticated user using a 3rd party extension - e.g. file upload in a contact form with knowing the target location. The attacked victim…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-pqg8-crx9-g8m4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11069

Advisory: Backend Same-Site Request Forgery in TYPO3 CMS
IDs: CVE-2020-11069, GHSA-pqg8-crx9-g8m4
Record: https://patchnext.com/advisories/cve-2020-11069 (revision 1, source checked 26 Oct 2026, 14:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-core 10.4.2, 9.5.17; typo3/cms 10.4.2, 9.5.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 9.0.0, < 9.5.17; >= 10.0.0, < 10.4.2; fixed in 9.5.17, 10.4.2
- Packagist typo3/cms: affected >= 10.0.0, < 10.4.2; >= 9.0.0, < 9.5.17; fixed in 9.5.17, 10.4.2

## Suggested inspection (read-only)
- Packagist typo3/cms-core: check the installed version with your package manager.
- Packagist typo3/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-core, typo3/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pqg8-crx9-g8m4 (GitHub-reviewed advisory GHSA-pqg8-crx9-g8m4 lists affected ranges: Packagist typo3/cms-core >=9.0.0 =10.0.0 =10.0.0 =9.0.0 <9.5.17)

Commands are suggestions: review each one before running it.

Loading voting…