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-3vmm-7h4j-69rmmedium4.2

TYPO3 vulnerable to Weak Authentication in Session Handling

Impact

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

Source excerpt · OSV
Applies when

It's important to note that exploiting this vulnerability requires a valid user account.

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 8.0.0 before 8.7.55Ecosystem versions8.7.55
From 9.0.0 before 9.5.44Ecosystem versions9.5.44
From 10.0.0 before 10.4.41Ecosystem versions10.4.41
From 11.0.0 before 11.5.33Ecosystem versions11.5.33
From 12.0.0 before 12.4.8Ecosystem versions12.4.8

Version evidence: OSV · GHSA-3vmm-7h4j-69rm

View original version evidence (167 explicit versions)

Original source description

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

Problem

Given that there are at least two different sites in the same TYPO3 installation - for instance first.example.org and second.example.com - then a session cookie generated for the first site can be reused on the second site without requiring additional authentication.

This vulnerability primarily affects the frontend of the website. It's important to note that exploiting this vulnerability requires a valid user account.

Solution

Update to TYPO3 versions 8.7.55 ELTS, 9.5.44 ELTS, 10.4.41 ELTS, 11.5.33, 12.4.8 that fix the problem described above.

Credits

Thanks to Rémy Daniel who reported this issue, and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.

References

References