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

GHSA-744g-7qm9-hjh9high7.2

The TYPO3 CMS Backend has Broken Authentication in Backend MFA

Check your stack

The advisory, in context

Problem

The multifactor authentication (MFA) dialog presented during backend login can be bypassed due to insufficient enforcement of access restrictions on all backend routes.

Successful exploitation requires valid backend user credentials, as MFA can only be bypassed after successful authentication.

Solution

Update to TYPO3 versions 12.4.31 LTS, 13.4.12 LTS that fix the problem described.

Credits

Thanks to Jens Jacobsen and Y. Kahveci for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it.

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.

Ecosystem versions

From 12.0.0 before 12.4.31

Fixed in 12.4.31

38 explicitly affected versions

v12.0.0, v12.1.0, v12.1.1, v12.1.2, v12.1.3, v12.2.0, v12.3.0, v12.4.0, v12.4.1, v12.4.10, v12.4.11, v12.4.12, v12.4.13, v12.4.14, v12.4.15, v12.4.16, v12.4.17, v12.4.18, v12.4.19, v12.4.2, v12.4.20, v12.4.21, v12.4.22, v12.4.23, v12.4.24, v12.4.25, v12.4.26, v12.4.27, v12.4.28, v12.4.29, v12.4.3, v12.4.30, v12.4.4, v12.4.5, v12.4.6, v12.4.7, v12.4.8, v12.4.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "12.0.0"
        },
        {
          "fixed": "12.4.31"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v12.0.0",
    "v12.1.0",
    "v12.1.1",
    "v12.1.2",
    "v12.1.3",
    "v12.2.0",
    "v12.3.0",
    "v12.4.0",
    "v12.4.1",
    "v12.4.10",
    "v12.4.11",
    "v12.4.12",
    "v12.4.13",
    "v12.4.14",
    "v12.4.15",
    "v12.4.16",
    "v12.4.17",
    "v12.4.18",
    "v12.4.19",
    "v12.4.2",
    "v12.4.20",
    "v12.4.21",
    "v12.4.22",
    "v12.4.23",
    "v12.4.24",
    "v12.4.25",
    "v12.4.26",
    "v12.4.27",
    "v12.4.28",
    "v12.4.29",
    "v12.4.3",
    "v12.4.30",
    "v12.4.4",
    "v12.4.5",
    "v12.4.6",
    "v12.4.7",
    "v12.4.8",
    "v12.4.9"
  ]
}
Ecosystem versions

From 13.0.0 before 13.4.12

Fixed in 13.4.12

19 explicitly affected versions

v13.0.0, v13.0.1, v13.1.0, v13.1.1, v13.2.1, v13.3.0, v13.3.1, v13.4.0, v13.4.1, v13.4.10, v13.4.11, v13.4.2, v13.4.3, v13.4.4, v13.4.5, v13.4.6, v13.4.7, v13.4.8, v13.4.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "13.0.0"
        },
        {
          "fixed": "13.4.12"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v13.0.0",
    "v13.0.1",
    "v13.1.0",
    "v13.1.1",
    "v13.2.1",
    "v13.3.0",
    "v13.3.1",
    "v13.4.0",
    "v13.4.1",
    "v13.4.10",
    "v13.4.11",
    "v13.4.2",
    "v13.4.3",
    "v13.4.4",
    "v13.4.5",
    "v13.4.6",
    "v13.4.7",
    "v13.4.8",
    "v13.4.9"
  ]
}

References