How severe is GHSA-wwjw-r3gj-39fq?

GHSA-wwjw-r3gj-39fq has a CVSS score of 6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-wwjw-r3gj-39fq?

GHSA-wwjw-r3gj-39fq affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wwjw-r3gj-39fq?

Update typo3/cms-core to 9.5.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwjw-r3gj-39fq is resolved across your whole dependency graph.

How do I detect GHSA-wwjw-r3gj-39fq in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wwjw-r3gj-39fq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wwjw-r3gj-39fq?

O3 pinpoints whether GHSA-wwjw-r3gj-39fq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wwjw-r3gj-39fq actively exploited in the wild?

No public exploit code has been indexed for GHSA-wwjw-r3gj-39fq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-wwjw-r3gj-39fq?

GHSA-wwjw-r3gj-39fq has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wwjw-r3gj-39fq?

GHSA-wwjw-r3gj-39fq is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wwjw-r3gj-39fq published, and has it been updated?

GHSA-wwjw-r3gj-39fq was published on June 17, 2022 and was last updated on December 6, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-wwjw-r3gj-39fq

MEDIUM

Insufficient Session Expiration in TYPO3's Admin Tool

Also known asBIT-typo3-2022-31050CVE-2022-31050

Published

Jun 17, 2022

Updated

Dec 6, 2023

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk63th percentile+0.72%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘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

Meta

CVSS: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L/E:F/RL:O/RC:C (5.6)

Problem

Admin Tool sessions initiated via the TYPO3 backend user interface have 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.

Solution

Update to TYPO3 versions 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.

Credits

Thanks to Kien Hoang who reported this issue and to TYPO3 framework merger Ralf Zimmermann and TYPO3 security member Oliver Hader who fixed the issue.

References

TYPO3-CORE-SA-2022-005

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 9.0.0&&< 9.5.35	9.5.35
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 10.4.29	10.4.29
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.11	11.5.11
🐘Packagist	`typo3/cms`	≥ 10.0.0&&< 10.4.29	10.4.29
🐘Packagist	`typo3/cms`	≥ 11.0.0&&< 11.5.11	11.5.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update typo3/cms-core to 9.5.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwjw-r3gj-39fq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wwjw-r3gj-39fq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wwjw-r3gj-39fq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L/E:F/RL:O/RC:C` (5.6) ### Problem Admin Tool sessions initiated via the TYPO3 backend user interface have 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. ### Solution Update to TYPO3 versions 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above. ### Credits Thanks to Kien Hoang who reported this issue and to TYPO3 framework merger Ralf Zimmermann and TY

O3 Security · Impact-Aware SCA

Is GHSA-wwjw-r3gj-39fq in your dependencies?

O3 detects GHSA-wwjw-r3gj-39fq across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works