{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4614 exists.","fix":"No fix has been published for CVE-2011-4614 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-4614 is a medium-severity code injection vulnerability in Typo3 Typo3, published on 18 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-4614 and fix it if it is affected.\n\nWhat it is: CVE-2011-4614 is a medium-severity code injection vulnerability in Typo3 Typo3, published on 18 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4614 exists.\n\nAffected product: Typo3 Typo3. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2011-4614/ (Markdown: https://insights.sbomify.com/CVE-2011-4614/index.md)","id":"CVE-2011-4614","markdown":"https://insights.sbomify.com/CVE-2011-4614/index.md","name":"CVE-2011-4614","record":{"aliases":["GHSA-h857-jmgh-2v5g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 workspaces extension","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code via a URL in the BACK_PATH parameter of the TYPO3 workspaces extension.","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.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"PHP remote file inclusion vulnerability in Classes/Controller/AbstractController.php in the workspaces system extension in TYPO3 4.5.x before 4.5.9, 4.6.x before 4.6.2, and development versions of 4.7 allows remote attackers to execute arbitrary PHP code via a URL in the BACK_PATH parameter.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2012-01-04","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2012-01-04","kind":"exploitdb","ref":"18308","stars":null,"title":"Typo3 4.5 \u003c 4.7 - Remote Code Execution / Local File Inclusion / Remote File Inclusion"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2011-4614","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"typo3:typo3","products":["typo3:typo3"],"type":"code_injection","year":"2011"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2011-4615"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2011-4613"},"products":["n/a"],"published":"2012-02-18","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":"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary PHP code via a URL in the BACK_PATH parameter of the TYPO3 workspaces extension.","url":"https://insights.sbomify.com/CVE-2011-4614/"}