GHSA-ppgf-8745-8pgx
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.
What each source reports
GitHub AdvisoriesNo score
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.
- Record
GHSA-ppgf-8745-8pgx- Weakness
- CWE-502
- Updated
- 2026-11-02
OSVNo score
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.
- Record
GHSA-ppgf-8745-8pgx- Weakness
- CWE-502
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
typo3/cmsPackagist | 7.0.0 up to 7.6.30 | 7.6.30 |
typo3/cmsPackagist | 8.0.0 up to 8.7.17 | 8.7.17 |
typo3/cmsPackagist | 9.0.0 up to 9.3.2 | 9.3.2 |
typo3/cmsPackagist | 7.0.0 up to 7.6.30, plus listed versions 7.0.17.0.27.1.07.2.07.3.0 Show 33 moreShow less7.3.17.4.07.5.07.6.07.6.17.6.107.6.117.6.127.6.137.6.147.6.157.6.167.6.177.6.187.6.197.6.27.6.37.6.47.6.57.6.67.6.77.6.87.6.9v7.6.20v7.6.21v7.6.22v7.6.23v7.6.24v7.6.25v7.6.26v7.6.27v7.6.28v7.6.29 | 7.6.30 |
typo3/cmsPackagist | 8.0.0 up to 8.7.17, plus listed versions 8.0.18.1.08.1.18.1.28.2.0 Show 26 moreShow less8.2.18.3.08.3.18.4.08.4.18.5.08.5.18.6.08.6.18.7.08.7.18.7.2v8.7.10v8.7.11v8.7.12v8.7.13v8.7.14v8.7.15v8.7.16v8.7.3v8.7.4v8.7.5v8.7.6v8.7.7v8.7.8v8.7.9 | 8.7.17 |
typo3/cmsPackagist | 9.0.0 up to 9.3.2, plus listed versions v9.0.0v9.1.0v9.2.0v9.2.1v9.3.0v9.3.1 | 9.3.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-ppgf-8745-8pgx is a vulnerability with no CVSS score yet in typo3/cms, published June 5, 2024. No source lists public exploit code. Fixed in typo3/cms 7.6.30.