cve.bz

CVE-2022-31050 typo3 typo3: Insufficient Session Expiration

7.2 highEPSS 1.3%Fix available

High (7.2) in typo3 typo3. EPSS 1.3% estimated probability of exploitation activity in the next 30 days. Fixed in typo3/cms-core 10.4.29, 11.5.11, 9.5.35.

On this page
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.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
1.3% (unchanged from 1.3% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 71st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-31050 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-31050?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-31050?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-31050 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
typo3:typo3from 9.0.0 before 9.5.35
typo3:typo3from 10.0.0 before 10.4.29
typo3:typo3from 11.0.0 before 11.5.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wwjw-r3gj-39fqPackagisttypo3/cms-core>=9.0.0 <9.5.359.5.35
GHSA-wwjw-r3gj-39fqPackagisttypo3/cms-core>=10.0.0 <10.4.2910.4.29
GHSA-wwjw-r3gj-39fqPackagisttypo3/cms-core>=11.0.0 <11.5.1111.5.11
GHSA-wwjw-r3gj-39fqPackagisttypo3/cms>=10.0.0 <10.4.2910.4.29
GHSA-wwjw-r3gj-39fqPackagisttypo3/cms>=11.0.0 <11.5.1111.5.11

References

Check your stackJSON