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-3r95-23jp-mhvgmedium5.4

Cross-Site Scripting in TYPO3's Form Framework

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

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.47Ecosystem versions8.7.47
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-3r95-23jp-mhvg

View original version evidence (122 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-3r95-23jp-mhvg

View original version evidence (55 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 (4.9)

Problem

It has been discovered that the Form Designer backend module of the Form Framework is vulnerable to cross-site scripting. A valid backend user account with access to the form module is needed to exploit this vulnerability.

Solution

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

Credits

Thanks to Gabe Troyan who reported and fixed the issue.

References

References