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-rgcg-28xm-8mmwmedium6.4

Cross-Site Scripting in Backend Grid View

Impact

Failing to properly encode settings for _backend layouts_, the corresponding grid view is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.

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 8.0.0 before 8.7.41Ecosystem versions8.7.41
From 9.0.0 before 9.5.28Ecosystem versions9.5.28
From 10.0.0 before 10.4.18Ecosystem versions10.4.18
From 11.0.0 before 11.3.1Ecosystem versions11.3.1

Version evidence: OSV · GHSA-rgcg-28xm-8mmw

View original version evidence (92 explicit versions)
typo3/cms Packagist
Affected rangeRecorded fix
From 10.0.0 before 10.4.18Ecosystem versions10.4.18
From 11.0.0 before 11.3.1Ecosystem versions11.3.1
From 9.0.0 before 9.5.28Ecosystem versions9.5.28

Version evidence: OSV · GHSA-rgcg-28xm-8mmw

View original version evidence (66 explicit versions)

Original source description

Problem

Failing to properly encode settings for backend layouts, the corresponding grid view is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.

Solution

Update to TYPO3 versions 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.

Credits

Thanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.

References