GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
Check your stack
GHSA-wwjw-r3gj-39fqmedium6.0

Insufficient Session Expiration in TYPO3's Admin Tool

Impact

> 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)

Source excerpt · OSV

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

typo3/cms-core Packagist
Affected rangeRecorded fix
From 9.0.0 before 9.5.35Ecosystem versions9.5.35
From 10.0.0 before 10.4.29Ecosystem versions10.4.29
From 11.0.0 before 11.5.11Ecosystem versions11.5.11

Version evidence: OSV · GHSA-wwjw-r3gj-39fq

View original version evidence (96 explicit versions)
typo3/cms Packagist
Affected rangeRecorded fix
From 10.0.0 before 10.4.29Ecosystem versions10.4.29
From 11.0.0 before 11.5.11Ecosystem versions11.5.11

Version evidence: OSV · GHSA-wwjw-r3gj-39fq

View original version evidence (55 explicit versions)

Original source 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

References