{"answers":{"affected":"4 open source packages ship an affected version, including typo3/cms-core.","exploited":"There is no known exploitation of GHSA-96jg-pmc4-cx39 in the wild and no public exploit code.","fix":"Upgrade typo3/cms-core to a fixed version for your release line: 8.7.17 or 9.3.1.","what":"GHSA-96jg-pmc4-cx39 is an unsafe deserialization vulnerability in typo3/cms-core, published on 30 May 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-96jg-pmc4-cx39 and fix it if it is affected.\n\nWhat it is: GHSA-96jg-pmc4-cx39 is an unsafe deserialization vulnerability in typo3/cms-core, published on 30 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-96jg-pmc4-cx39 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms-core (Packagist): affected from 8.5.0; fixed in 8.7.17\n- typo3/cms-core (Packagist): affected from 8.5.0; fixed in 8.7.17\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.3.1\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.3.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-96jg-pmc4-cx39/ (Markdown: https://insights.sbomify.com/GHSA-96jg-pmc4-cx39/index.md)","id":"GHSA-96jg-pmc4-cx39","markdown":"https://insights.sbomify.com/GHSA-96jg-pmc4-cx39/index.md","name":"GHSA-96jg-pmc4-cx39","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 Form Framework","requires_auth":"high_privilege","summary":"Authenticated backend users can achieve remote code execution via insecure deserialization in the TYPO3 Form Framework when using the yaml PECL package.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"It has been discovered that the Form Framework (system extension `form`) is vulnerable to Insecure Deserialization when being used with the additional PHP PECL package `yaml`, which is capable of unserializing YAML contents to PHP objects. A valid backend user account as well as having PHP setting `yaml.decode_php` enabled is needed to exploit this vulnerability (which is the default value according to PHP documentation).","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"TYPO3 CMS Insecure Deserialization","id":"GHSA-96jg-pmc4-cx39","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["8.7.17"],"introduced":["8.5.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-96jg-pmc4-cx39"},{"ecosystem":"Packagist","fixed":["8.7.17"],"introduced":["8.5.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-96jg-pmc4-cx39"},{"ecosystem":"Packagist","fixed":["9.3.1"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-96jg-pmc4-cx39"},{"ecosystem":"Packagist","fixed":["9.3.1"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-96jg-pmc4-cx39"}],"products":null,"published":"2024-05-30","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Authenticated backend users can achieve remote code execution via insecure deserialization in the TYPO3 Form Framework when using the yaml PECL package.","url":"https://insights.sbomify.com/GHSA-96jg-pmc4-cx39/"}