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-38r2-5695-334wmedium4.3

TYPO3 Backend Forms vulnerable to Information Disclosure of Hashed Passwords

Impact

Password hashes were being reflected in the editing forms of the TYPO3 backend user interface. This allowed attackers to crack the plaintext password using brute force techniques. Exploiting this vulnerability requires a valid backend user account.

Source excerpt · OSV
Applies when

Exploiting this vulnerability requires a valid backend 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.57Ecosystem versions8.7.57
From 9.0.0 before 9.5.46Ecosystem versions9.5.46
From 10.0.0 before 10.4.43Ecosystem versions10.4.43
From 11.0.0 before 11.5.35Ecosystem versions11.5.35
From 12.0.0 before 12.4.11Ecosystem versions12.4.11
From 13.0.0 before 13.0.1Ecosystem versions13.0.1

Version evidence: OSV · GHSA-38r2-5695-334w

View original version evidence (174 explicit versions)

Original source description

Problem

Password hashes were being reflected in the editing forms of the TYPO3 backend user interface. This allowed attackers to crack the plaintext password using brute force techniques. Exploiting this vulnerability requires a valid backend user account.

Solution

Update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.

Credits

Thanks to the TYPO3 framework merger Christian Kuhn and external security researchers Maximilian Beckmann, Klaus-Günther Schmidt who reported this issue, and TYPO3 security team member Oliver Hader who fixed the issue.

References

References