{"items":[{"id":"NVI-00007454","kind":"vulnerability","title":"TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-cc97-g92w-jm65"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.17 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-dc6bd8e19ae830962cdfb7b6e1517018"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 9.3.2 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-dc6bd8e19ae830962cdfb7b6e1517018"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.6.30 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-dc6bd8e19ae830962cdfb7b6e1517018"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-dc6bd8e19ae830962cdfb7b6e1517018","url":"https://github.com/advisories/GHSA-cc97-g92w-jm65","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-cc97-g92w-jm65","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.698Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-dc6bd8e19ae830962cdfb7b6e1517018"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"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.","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.17"]},{"certainty":"source_listed","source_ids":["sr-dc6bd8e19ae830962cdfb7b6e1517018"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"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.","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.3.2"]},{"certainty":"source_listed","source_ids":["sr-dc6bd8e19ae830962cdfb7b6e1517018"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"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.","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.30"]}],"null_published_at":"2026-10-31T22:13:18.620Z","source_updated_at":"2024-12-05T05:43:00.905Z","source_disclosed_at":"2024-05-30T13:52:08.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:10.698Z"}],"next_cursor":null,"snapshot_revision":"42594"}