Summary
Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS
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.
Impact
Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
typo3/cms to 7.6.30 or later; typo3/cms to 8.7.17 or later; typo3/cms to 9.3.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-PPGF-8745-8PGX? GHSA-PPGF-8745-8PGX is a high-severity insecure deserialization vulnerability in typo3/cms (composer), affecting versions >= 7.0.0, < 7.6.30. It is fixed in 7.6.30, 8.7.17, 9.3.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
- Which versions of typo3/cms are affected by GHSA-PPGF-8745-8PGX? typo3/cms (composer) versions >= 7.0.0, < 7.6.30 is affected.
- Is there a fix for GHSA-PPGF-8745-8PGX? Yes. GHSA-PPGF-8745-8PGX is fixed in 7.6.30, 8.7.17, 9.3.2. Upgrade to this version or later.
- Is GHSA-PPGF-8745-8PGX exploitable, and should I be worried? Whether GHSA-PPGF-8745-8PGX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-PPGF-8745-8PGX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-PPGF-8745-8PGX?
- Upgrade
typo3/cmsto 7.6.30 or later - Upgrade
typo3/cmsto 8.7.17 or later - Upgrade
typo3/cmsto 9.3.2 or later
- Upgrade