Advisory record · GHSA-wwjw-r3gj-39fq

Insufficient Session Expiration in TYPO3's Admin Tool

CVSS 6.0 MediumEPSS 0.013 · 70th percentile

Published by the GitHub Advisory Database at 17 Jun 2022, 20:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typo3/cms-corePackagist>=9.0.0, <9.5.35 || >=10.0.0, <10.4.29 || >=11.0.0, <11.5.119.5.35, 10.4.29, 11.5.11
typo3/cmsPackagist>=10.0.0, <10.4.29 || >=11.0.0, <11.5.1110.4.29, 11.5.11
Identifiers
GHSA-wwjw-r3gj-39fq · BIT-typo3-2022-31050 · CVE-2022-31050 · PKSA-2hf7-8md4-q2c6 · PKSA-dnvg-71td-yz19
Weakness (CWE)
CWE-613
Published
17 Jun 2022
Updated
6 Dec 2023

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Sessions in the TYPO3 Admin Tool (typo3/cms-core and typo3/cms) were not revoked when the related backend user account was downgraded or disabled, so these sessions could stay active without limit. The source indicates an attacker would need an account with high privileges (the CVSS vector lists high privileges required) and could then keep admin tool access after the account lost its rights; the source gives few further details. Upgrade typo3/cms-core to 9.5.35, 10.4.29, or 11.5.11, and typo3/cms to 10.4.29 or 11.5.11.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.0 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.013, the 70th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:32 UTC First seen by agentprime
  2. 31 Oct 2026, 14:32 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.