NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

TYPO3 CMS vulnerable to Insufficient Session Expiration after Password ResetGHSA-mgj2-q8wp-29rr

MEDIUMFix: TYPO3/typo3@d9ffbf2

GHSA-mgj2-q8wp-29rr is a medium-severity (CVSS 5.4) CWE-613 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

Also known asBIT-typo3-2022-23502CVE-2022-23502
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mgj2-q8wp-29rr.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk
0.00%0.31%0.62%0.93%0.2%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected
🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Problem

When users reset their password using the corresponding password recovery functionality, existing sessions for that particular user account were not revoked. This applied to both frontend user sessions and backend user sessions.

Solution

Update to TYPO3 versions 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.

References

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-core≥ 10.0.0&&< 10.4.3310.4.33composer require typo3/cms-core:^10.4.33
🐘Packagisttypo3/cms-core≥ 11.0.0&&< 11.5.2011.5.20composer require typo3/cms-core:^11.5.20
🐘Packagisttypo3/cms-core≥ 12.0.0&&< 12.1.112.1.1composer require typo3/cms-core:^12.1.1
🐘Packagisttypo3/cms≥ 10.0.0&&< 10.4.3310.4.33composer require typo3/cms:^10.4.33
🐘Packagisttypo3/cms≥ 11.0.0&&< 11.5.2011.5.20composer require typo3/cms:^11.5.20
🐘Packagisttypo3/cms≥ 12.0.0&&< 12.1.112.1.1composer require typo3/cms:^12.1.1

Affected Products

1 product · 3 configurations
Application
typo3typo3
≥ 12.0.0 && < 12.1.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update typo3/cms-core to 10.4.33 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgj2-q8wp-29rr is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Problem When users reset their password using the corresponding password recovery functionality, existing sessions for that particular user account were not revoked. This applied to both frontend user sessions and backend user sessions. ### Solution Update to TYPO3 versions 10.4.33, 11.5.20, 12.1.1 that fix the problem described above. ### References * [TYPO3-CORE-SA-2022-014](https://typo3.org/security/advisory/typo3-core-sa-2022-014)
O3 Security · Impact-Aware SCA

Is GHSA-mgj2-q8wp-29rr in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
TYPO3 CMS vulnerable to Insufficient Session Expiration…