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

Check your stack
GHSA-9c6w-55cp-5w25medium5.4

TYPO3 CMS Stored Cross-Site Scripting via FileDumpController

Impact

> Meta > CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (5.0)

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.

Affected rangeRecorded fix
From 7.0.0 before 7.6.58Ecosystem versions7.6.58
From 8.0.0 before 8.7.48Ecosystem versions8.7.48
From 9.0.0 before 9.5.37Ecosystem versions9.5.37
From 10.0.0 before 10.4.32Ecosystem versions10.4.32
From 11.0.0 before 11.5.16Ecosystem versions11.5.16

Version evidence: OSV · GHSA-9c6w-55cp-5w25

View original version evidence (130 explicit versions)
typo3/cms Packagist
Affected rangeRecorded fix
From 10.0.0 before 10.4.32Ecosystem versions10.4.32
From 11.0.0 before 11.5.16Ecosystem versions11.5.16

Version evidence: OSV · GHSA-9c6w-55cp-5w25

View original version evidence (63 explicit versions)

Original source description

Meta

  • CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (5.0)

Problem

It has been discovered that the FileDumpController (backend and frontend context) is vulnerable to cross-site scripting when malicious files are displayed using this component. A valid backend user account is needed to exploit this vulnerability.

Solution

Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.

Credits

Thanks to Vautia who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.

References

References