{"answers":{"affected":"4 open source packages ship an affected version, including typo3/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-4321 in the wild and no public exploit code.","fix":"Upgrade typo3/cms to a fixed version for your release line: 6.0.9 or 6.1.4.","what":"CVE-2013-4321 is a medium-severity code injection vulnerability in Typo3 Typo3, published on 20 May 2014. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-4321 and fix it if it is affected.\n\nWhat it is: CVE-2013-4321 is a medium-severity code injection vulnerability in Typo3 Typo3, published on 20 May 2014. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-4321 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 6.0.0; fixed in 6.0.9\n- typo3/cms (Packagist): affected from 6.0.0; fixed in 6.0.9\n- typo3/cms (Packagist): affected from 6.1.0; fixed in 6.1.4\n- typo3/cms (Packagist): affected from 6.1.0; fixed in 6.1.4\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-2013-4321/ (Markdown: https://insights.sbomify.com/CVE-2013-4321/index.md)","id":"CVE-2013-4321","markdown":"https://insights.sbomify.com/CVE-2013-4321/index.md","name":"CVE-2013-4321","record":{"aliases":["GHSA-m76j-69c2-c3m8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"low_privilege","summary":"Authenticated editors can execute arbitrary PHP code by manipulating file extensions during renaming in TYPO3.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The File Abstraction Layer (FAL) in TYPO3 6.0.x before 6.0.8 and 6.1.x before 6.1.4 allows remote authenticated editors to execute arbitrary PHP code via unspecified characters in the file extension when renaming a file.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-4250.","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 remote authenticated arbitrary code execution","id":"CVE-2013-4321","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"typo3:typo3","products":["typo3:typo3"],"type":"code_injection","year":"2013"},"n_packages":4,"n_references":1,"next":{"headline":"Apache Tomcat Denial of Service vulnerability","id":"CVE-2013-4322"},"packages":[{"ecosystem":"Packagist","fixed":["6.0.9"],"introduced":["6.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-m76j-69c2-c3m8"},{"ecosystem":"Packagist","fixed":["6.0.9"],"introduced":["6.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-m76j-69c2-c3m8"},{"ecosystem":"Packagist","fixed":["6.1.4"],"introduced":["6.1.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-m76j-69c2-c3m8"},{"ecosystem":"Packagist","fixed":["6.1.4"],"introduced":["6.1.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-m76j-69c2-c3m8"}],"prev":{"headline":"TYPO3 Improper Access Management in the File Abstraction Layer","id":"CVE-2013-4320"},"products":["n/a"],"published":"2014-05-20","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Authenticated editors can execute arbitrary PHP code by manipulating file extensions during renaming in TYPO3.","url":"https://insights.sbomify.com/CVE-2013-4321/"}