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
All vulnerabilities
GHSA-cc97-g92w-jm65critical9.8

TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution

No CVE assignedCheck your stack

The advisory, in context

Phar files (formerly known as "PHP archives") can act als self extracting archives which leads to the fact that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored with a dedicated file extension - "bundle.phar" would be valid as well as "bundle.txt" would be. This way, Phar files can be obfuscated as image or text file which would not be denied from being uploaded and persisted to a TYPO3 installation. Due to a missing sanitization of user input, those Phar files can be invoked by manipulated URLs in TYPO3 backend forms. A valid backend user account is needed to exploit this vulnerability. In theory the attack vector would be possible in the TYPO3 frontend as well, however no functional exploit has been identified so far.

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 8.0.0 before 8.7.17

Fixed in 8.7.17

10 explicitly affected versions

v8.7.10, v8.7.11, v8.7.12, v8.7.13, v8.7.14, v8.7.15, v8.7.16, v8.7.7, v8.7.8, v8.7.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "8.0.0"
        },
        {
          "fixed": "8.7.17"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v8.7.10",
    "v8.7.11",
    "v8.7.12",
    "v8.7.13",
    "v8.7.14",
    "v8.7.15",
    "v8.7.16",
    "v8.7.7",
    "v8.7.8",
    "v8.7.9"
  ]
}
Ecosystem versions

From 9.0.0 before 9.3.2

Fixed in 9.3.2

6 explicitly affected versions

v9.0.0, v9.1.0, v9.2.0, v9.2.1, v9.3.0, v9.3.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "9.0.0"
        },
        {
          "fixed": "9.3.2"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v9.0.0",
    "v9.1.0",
    "v9.2.0",
    "v9.2.1",
    "v9.3.0",
    "v9.3.1"
  ]
}
Ecosystem versions

From 7.0.0 before 7.6.30

Fixed in 7.6.30

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "7.0.0"
        },
        {
          "fixed": "7.6.30"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": []
}

References