{"answers":{"affected":"5 open source packages ship an affected version, including typo3/cms, typo3 and typo3/cms-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41113 in the wild and no public exploit code.","fix":"Upgrade typo3/cms to 11.5.0 or later.","what":"CVE-2021-41113 is a high-severity vulnerability in Typo3 Typo3, published on 5 Oct 2021. 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 CVE-2021-41113 and fix it if it is affected.\n\nWhat it is: CVE-2021-41113 is a high-severity vulnerability in Typo3 Typo3, published on 5 Oct 2021. 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 CVE-2021-41113 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 11.2.0; fixed in 11.5.0\n- typo3/cms (Packagist): affected from 11.2.0; fixed in 11.5.0\n- typo3 (Bitnami): affected from 11.2.0; fixed in 11.5.0\n- typo3/cms-core (Packagist): affected from 11.2.0; fixed in 11.5.0\n- typo3/cms-core (Packagist): affected from 11.2.0; fixed in 11.5.0\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-2021-41113/ (Markdown: https://insights.sbomify.com/CVE-2021-41113/index.md)","id":"CVE-2021-41113","markdown":"https://insights.sbomify.com/CVE-2021-41113/index.md","name":"CVE-2021-41113","record":{"aliases":["BIT-typo3-2021-41113","GHSA-657m-v5vm-f6rw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"TYPO3 CMS","requires_auth":"none","summary":"Attackers can exploit CSRF in TYPO3 backend deep links to create admin accounts if specific cookie settings are used.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"TYPO3 is an open source PHP based web content management system released under the GNU GPL. It has been discovered that the new TYPO3 v11 feature that allows users to create and share deep links in the backend user interface is vulnerable to cross-site-request-forgery. The impact is the same as described in TYPO3-CORE-SA-2020-006 (CVE-2020-11069). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system. To successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time. The following Same-Site cookie settings in $GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite] are required for an attack to be successful: SameSite=strict: malicious evil.example.org invoking TYPO3 application at good.example.org and SameSite=lax or none: malicious evil.com invoking TYPO3 application at example.org. Update your instance to TYPO3 version 11.5.0 which addresses the problem described.","ecosystems":["Bitnami","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":"Cross-Site-Request-Forgery in Backend URI Handling in Typo3","id":"CVE-2021-41113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"typo3:typo3","products":["typo3:typo3"],"type":"csrf","year":"2021"},"n_packages":5,"n_references":3,"next":{"headline":"HTTP Host Header Injection in Request Handling in Typo3","id":"CVE-2021-41114"},"packages":[{"ecosystem":"Bitnami","fixed":["11.5.0"],"introduced":["11.2.0"],"last_affected":[],"package":"typo3","purl":"pkg:bitnami/typo3","source":"BIT-typo3-2021-41113"},{"ecosystem":"Packagist","fixed":["11.5.0"],"introduced":["11.2.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-657m-v5vm-f6rw"},{"ecosystem":"Packagist","fixed":["11.5.0"],"introduced":["11.2.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-657m-v5vm-f6rw"},{"ecosystem":"Packagist","fixed":["11.5.0"],"introduced":["11.2.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-657m-v5vm-f6rw"},{"ecosystem":"Packagist","fixed":["11.5.0"],"introduced":["11.2.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-657m-v5vm-f6rw"}],"prev":{"headline":"Missing Authorization in Rundeck","id":"CVE-2021-41112"},"products":["typo3"],"published":"2021-10-05","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":"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":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["TYPO3"]},"summary":"Attackers can exploit CSRF in TYPO3 backend deep links to create admin accounts if specific cookie settings are used.","url":"https://insights.sbomify.com/CVE-2021-41113/"}