{"answers":{"affected":"2 open source packages ship an affected version, including typo3/cms-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-34355 in the wild and no public exploit code.","fix":"Upgrade typo3/cms-core to 13.1.1 or later.","what":"CVE-2024-34355 is a low-severity cross-site scripting vulnerability in Typo3 Typo3, published on 14 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-34355 and fix it if it is affected.\n\nWhat it is: CVE-2024-34355 is a low-severity cross-site scripting vulnerability in Typo3 Typo3, published on 14 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-34355 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.1.1\n- typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.1.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/CVE-2024-34355/ (Markdown: https://insights.sbomify.com/CVE-2024-34355/index.md)","id":"CVE-2024-34355","markdown":"https://insights.sbomify.com/CVE-2024-34355/index.md","name":"CVE-2024-34355","record":{"aliases":["GHSA-xjwx-78x7-q6jc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"low_privilege","summary":"Authenticated backend users can inject malicious HTML into the TYPO3 history module, potentially altering displayed content despite CSP protections.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"TYPO3 is an enterprise content management system. Starting in version 13.0.0 and prior to version 13.1.1, the history backend module is vulnerable to HTML injection. Although Content-Security-Policy headers effectively prevent JavaScript execution, adversaries can still inject malicious HTML markup. Exploiting this vulnerability requires a valid backend user account. TYPO3 version 13.1.1 fixes the problem described.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"TYPO3 vulnerable to an HTML Injection in the History Module","id":"CVE-2024-34355","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"typo3:typo3","products":["typo3:typo3"],"type":"xss","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"TYPO3 vulnerable to Cross-Site Scripting in the Form Manager Module","id":"CVE-2024-34356"},"packages":[{"ecosystem":"Packagist","fixed":["13.1.1"],"introduced":["13.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-xjwx-78x7-q6jc"},{"ecosystem":"Packagist","fixed":["13.1.1"],"introduced":["13.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-xjwx-78x7-q6jc"}],"prev":{"headline":"CMSaasStarter: JWT Token Not Verified on Server Session","id":"CVE-2024-34354"},"products":["typo3"],"published":"2024-05-14","related":[{"cvss_score":10,"headline":"Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection","id":"CVE-2009-0258","kev_date_added":null,"published":"2009-01-22"},{"cvss_score":9.8,"headline":"Typo3 SQL injection due to faulty prepared statements","id":"CVE-2011-3583","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":9.8,"headline":"Typo3 Authentication Bypass","id":"CVE-2011-4628","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":8.8,"headline":"Persisted Cross-Site Scripting in Frontend Rendering in typo3","id":"CVE-2023-24814","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":8.8,"headline":"Cross-Site-Request-Forgery in Backend URI Handling in Typo3","id":"CVE-2021-41113","kev_date_added":null,"published":"2021-10-05"},{"cvss_score":8.8,"headline":"Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS","id":"CVE-2020-15098","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in TYPO3 CMS","id":"CVE-2020-11067","kev_date_added":null,"published":"2020-05-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["TYPO3"]},"summary":"Authenticated backend users can inject malicious HTML into the TYPO3 history module, potentially altering displayed content despite CSP protections.","url":"https://insights.sbomify.com/CVE-2024-34355/"}