LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31050: Insufficient Session Expiration in TYPO3 Admin Tool

TYPO3 is an open source web content management system. Prior to versions 9.5.34 ELTS, 10.4.29, and 11.5.11, Admin Tool sessions initiated via the TYPO3 backend user interface had not been revoked even if the corresponding user account was degraded to lower permissions or disabled completely. This way, sessions in the admin tool theoretically could have been prolonged without any limit. TYPO3 versions 9.5.34 ELTS, 10.4.29, and 11.5.11 contain a fix for the problem.

MediumCVSS 6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

TYPO3 Admin Tool sessions could remain usable after an administrator’s backend account was disabled or reduced in permissions. This could leave a former privileged session alive longer than intended. The issue is fixed in TYPO3 9.5.34 ELTS, 10.4.29, and 11.5.11.

Executive priority

Schedule remediation in the normal security patch cycle, with faster action for systems with many administrators or recent staff changes. The issue is not reported as actively exploited, but it weakens a critical administrative control.

Technical view

CVE-2022-31050 is CWE-613 insufficient session expiration in TYPO3. Admin Tool sessions started from the backend UI were not revoked when the related backend user was disabled or downgraded. Affected branches are 9.x before 9.5.34 ELTS, 10.x before 10.4.29, and 11.x before 11.5.11.

Likely exposure

Exposure is limited to TYPO3 deployments running the affected versions where backend users can access the Admin Tool. The CVSS vector requires high privileges, but impact can be serious because an already-established Admin Tool session may retain access despite account restriction.

Exploitation context

The provided sources describe theoretical unlimited session prolongation. They do not cite active exploitation, and this CVE is not listed as KEV in the supplied bundle. Treat it as a privileged session-control flaw rather than a remotely exploitable unauthenticated issue.

Researcher notes

The strongest evidence is the TYPO3 advisory and GitHub advisory. The commit reference supports that a code fix exists, but the supplied bundle does not include exploit details or independent exploitation reporting. Avoid expanding scope beyond TYPO3 core Admin Tool sessions.

Mitigation direction

  • Upgrade TYPO3 to 9.5.34 ELTS, 10.4.29, 11.5.11, or later.
  • Review TYPO3’s official advisory for branch-specific guidance.
  • Limit Admin Tool access to users with a current operational need.
  • Review disabled or downgraded backend accounts for recently active sessions.
  • Apply standard post-upgrade session invalidation procedures if vendor guidance recommends them.

Validation and detection

  • Inventory TYPO3 versions across production, staging, and managed customer instances.
  • Confirm no deployed instance is below the fixed version for its branch.
  • Review backend user permission changes around Admin Tool access.
  • Check logs for unusually long-lived Admin Tool sessions after account downgrades or disablement.
  • In staging, verify disabled backend users cannot retain Admin Tool access after patching.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-613: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31050 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L1.24.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6Medium
CVSS 3.1 vector shape for CVE-2022-31050Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TYPO3typo3>= 9.0.0, < 9.5.34, >= 10.0.0, < 10.4.29, >= 11.0.0, < 11.5.11Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.