TYPO3 CMS missing check for expiration time of password reset token for backend users

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-36106: 0.95% estimated exploitation activity in the next 30 days; percentile 61.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Meta CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N/E:F/RL:O/RC:C (5.0) Problem It has been discovered that the expiration time of a password reset link for TYPO3 backend users has never been evaluated. As a result, a password reset link could be used to perform a password reset even if the default expiry time of two hours has been exceeded. Solution Update to TYPO3 version 10.4.32 or 11.5.16 that fix the problem described above. Credits Thanks to Ingo Fabbri who reported this issue and to TYPO3 security team member Torben Hansen who fixed the issue. References TYPO3-CORE-SA-2022-008

Published by the source

16 Sep 2022, 17:16 UTC

Last modified by the source

27 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 13:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5959-4x58-r8c2

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

# Patch Next advisory brief: CVE-2022-36106

Advisory: TYPO3 CMS missing check for expiration time of password reset token for backend users
IDs: CVE-2022-36106, GHSA-5959-4x58-r8c2
Record: https://patchnext.com/advisories/cve-2022-36106 (revision 1, source checked 26 Oct 2026, 13:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
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 11.5.16, 10.4.32; typo3/cms 11.5.16, 10.4.32. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 10.4.0, < 10.4.32; >= 11.0.0, < 11.5.16; fixed in 11.5.16, 10.4.32
- Packagist typo3/cms: affected >= 10.4.0, < 10.4.32; >= 11.0.0, < 11.5.16; fixed in 11.5.16, 10.4.32

## 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-5959-4x58-r8c2 (GitHub-reviewed advisory GHSA-5959-4x58-r8c2 lists affected ranges: Packagist typo3/cms-core >=10.4.0 =11.0.0 =10.4.0 =11.0.0 <11.5.16)

Commands are suggestions: review each one before running it.