Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS

GHSA-ppgf-8745-8pgx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 9.3.2, 8.7.17, 7.6.30), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms

    Affected
    >= 7.0.0, < 7.6.30>= 8.0.0, < 8.7.17>= 9.0.0, < 9.3.2
    Fixed in
    7.6.30, 9.3.2, 8.7.17

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-ppgf-8745-8pgx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-ppgf-8745-8pgx

Advisory: Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS
IDs: GHSA-ppgf-8745-8pgx
Record: https://patchnext.com/advisories/ghsa-ppgf-8745-8pgx (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 9.3.2, 8.7.17, 7.6.30. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected >= 7.0.0, < 7.6.30; >= 8.0.0, < 8.7.17; >= 9.0.0, < 9.3.2; fixed in 7.6.30, 9.3.2, 8.7.17

## Suggested inspection (read-only)
- Packagist typo3/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ppgf-8745-8pgx (GitHub-reviewed advisory GHSA-ppgf-8745-8pgx lists affected ranges: Packagist typo3/cms >=7.0.0 =8.0.0 =9.0.0 <9.3.2)

Commands are suggestions: review each one before running it.

Loading voting…