{"answers":{"affected":"4 open source packages ship an affected version, including typo3/cms.","exploited":"There is no known exploitation of GHSA-7qwg-fcpw-xg5g in the wild and no public exploit code.","fix":"Upgrade typo3/cms to a fixed version for your release line: 8.7.17 or 9.3.2.","what":"GHSA-7qwg-fcpw-xg5g is a SQL injection vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-7qwg-fcpw-xg5g and fix it if it is affected.\n\nWhat it is: GHSA-7qwg-fcpw-xg5g is a SQL injection vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-7qwg-fcpw-xg5g in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 8.5.0; fixed in 8.7.17\n- typo3/cms (Packagist): affected from 8.5.0; fixed in 8.7.17\n- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.3.2\n- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.3.2\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-7qwg-fcpw-xg5g/ (Markdown: https://insights.sbomify.com/GHSA-7qwg-fcpw-xg5g/index.md)","id":"GHSA-7qwg-fcpw-xg5g","markdown":"https://insights.sbomify.com/GHSA-7qwg-fcpw-xg5g/index.md","name":"GHSA-7qwg-fcpw-xg5g","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"TYPO3 CMS Form Framework","requires_auth":"low_privilege","summary":"Authenticated backend users can exploit SQL injection and privilege escalation in the TYPO3 Form Framework to execute arbitrary code.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Failing to properly dissociate system related configuration from user generated configuration, the Form Framework (system extension \"form\") is vulnerable to SQL injection and Privilege Escalation. Basically instructions can be persisted to a form definition file that were not configured to be modified - this applies to definitions managed using the form editor module as well as direct file upload using the regular file list module. A valid backend user account as well as having system extension form activated are needed in order to exploit this vulnerability.","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":"Privilege Escalation \u0026 SQL Injection in TYPO3 CMS","id":"GHSA-7qwg-fcpw-xg5g","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["8.7.17"],"introduced":["8.5.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-7qwg-fcpw-xg5g"},{"ecosystem":"Packagist","fixed":["8.7.17"],"introduced":["8.5.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-7qwg-fcpw-xg5g"},{"ecosystem":"Packagist","fixed":["9.3.2"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-7qwg-fcpw-xg5g"},{"ecosystem":"Packagist","fixed":["9.3.2"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-7qwg-fcpw-xg5g"}],"products":null,"published":"2024-06-05","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 exploit SQL injection and privilege escalation in the TYPO3 Form Framework to execute arbitrary code.","url":"https://insights.sbomify.com/GHSA-7qwg-fcpw-xg5g/"}