{"answers":{"affected":"8 open source packages ship an affected version, including typo3/cms.","exploited":"There is no known exploitation of GHSA-mxjf-hc9v-xgv2 in the wild and no public exploit code.","fix":"Upgrade typo3/cms to a fixed version for your release line: 4.5.34, 4.7.19, 6.1.9 or 6.2.3.","what":"GHSA-mxjf-hc9v-xgv2 is a cross-site scripting vulnerability in typo3/cms, published on 30 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-mxjf-hc9v-xgv2 and fix it if it is affected.\n\nWhat it is: GHSA-mxjf-hc9v-xgv2 is a cross-site scripting vulnerability in typo3/cms, published on 30 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-mxjf-hc9v-xgv2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 4.5.0; fixed in 4.5.34\n- typo3/cms (Packagist): affected from 4.5.0; fixed in 4.5.34\n- typo3/cms (Packagist): affected from 4.7.0; fixed in 4.7.19\n- typo3/cms (Packagist): affected from 4.7.0; fixed in 4.7.19\n- typo3/cms (Packagist): affected from 6.1.0; fixed in 6.1.9\n- typo3/cms (Packagist): affected from 6.1.0; fixed in 6.1.9\n- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.3\n- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.3\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-mxjf-hc9v-xgv2/ (Markdown: https://insights.sbomify.com/GHSA-mxjf-hc9v-xgv2/index.md)","id":"GHSA-mxjf-hc9v-xgv2","markdown":"https://insights.sbomify.com/GHSA-mxjf-hc9v-xgv2/index.md","name":"GHSA-mxjf-hc9v-xgv2","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"none","summary":"Attackers can exploit host header spoofing in TYPO3 to inject malicious scripts, potentially stealing user data or bypassing security controls.","user_interaction":"required","vuln_class":"xss"},"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 validate the HTTP host-header TYPO3 CMS is susceptible to host spoofing. TYPO3 uses the HTTP host-header to generate absolute URLs in several places like 404 handling, http(s) enforcement, password reset links and many more. Since the host header itself is provided by the client it can be forged to any value, even in a name based virtual hosts environment. A blog post describes this problem in great detail.","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":"ExtJS JavaScript framework used in TYPO3 vulnerable to Cross-site Scripting","id":"GHSA-mxjf-hc9v-xgv2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":8,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["4.5.34"],"introduced":["4.5.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-mxjf-hc9v-xgv2"},{"ecosystem":"Packagist","fixed":["4.5.34"],"introduced":["4.5.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-mxjf-hc9v-xgv2"},{"ecosystem":"Packagist","fixed":["4.7.19"],"introduced":["4.7.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-mxjf-hc9v-xgv2"},{"ecosystem":"Packagist","fixed":["4.7.19"],"introduced":["4.7.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-mxjf-hc9v-xgv2"},{"ecosystem":"Packagist","fixed":["6.1.9"],"introduced":["6.1.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-mxjf-hc9v-xgv2"},{"ecosystem":"Packagist","fixed":["6.1.9"],"introduced":["6.1.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-mxjf-hc9v-xgv2"},{"ecosystem":"Packagist","fixed":["6.2.3"],"introduced":["6.2.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-mxjf-hc9v-xgv2"},{"ecosystem":"Packagist","fixed":["6.2.3"],"introduced":["6.2.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-mxjf-hc9v-xgv2"}],"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":"Attackers can exploit host header spoofing in TYPO3 to inject malicious scripts, potentially stealing user data or bypassing security controls.","url":"https://insights.sbomify.com/GHSA-mxjf-hc9v-xgv2/"}