{"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-2020-26229 in the wild and no public exploit code.","fix":"Upgrade typo3/cms to 10.4.10 or later.","what":"CVE-2020-26229 is a low-severity vulnerability in Typo3 Typo3, published on 23 Nov 2020. 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-2020-26229 and fix it if it is affected.\n\nWhat it is: CVE-2020-26229 is a low-severity vulnerability in Typo3 Typo3, published on 23 Nov 2020. 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-2020-26229 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.10\n- typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.10\n- typo3 (Bitnami): affected from 10.0.0; fixed in 10.4.10\n- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.10\n- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.10\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-2020-26229/ (Markdown: https://insights.sbomify.com/CVE-2020-26229/index.md)","id":"CVE-2020-26229","markdown":"https://insights.sbomify.com/CVE-2020-26229/index.md","name":"CVE-2020-26229","record":{"aliases":["BIT-typo3-2020-26229","GHSA-q9cp-mc96-m4w2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"TYPO3 CMS","requires_auth":"low_privilege","summary":"Authenticated backend users could exploit XML External Entity vulnerabilities in RSS widgets to read sensitive data, though default configurations mitigate this risk.","user_interaction":"required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"TYPO3 is an open source PHP based web content management system. In TYPO3 from version 10.4.0, and before version 10.4.10, RSS widgets are susceptible to XML external entity processing. This vulnerability is reasonable, but is theoretical - it was not possible to actually reproduce the vulnerability with current PHP versions of supported and maintained system distributions. At least with libxml2 version 2.9, the processing of XML external entities is disabled per default - and cannot be exploited. Besides that, a valid backend user account is needed. Update to TYPO3 version 10.4.10 to fix 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":"XML External Entity in Dashboard Widget","id":"CVE-2020-26229","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"typo3:typo3","products":["typo3:typo3"],"type":"xxe","year":"2020"},"n_packages":5,"n_references":2,"next":{"headline":"Deanonymization of COVID-19 positive users of Radar COVID","id":"CVE-2020-26230"},"packages":[{"ecosystem":"Bitnami","fixed":["10.4.10"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3","purl":"pkg:bitnami/typo3","source":"BIT-typo3-2020-26229"},{"ecosystem":"Packagist","fixed":["10.4.10"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-q9cp-mc96-m4w2"},{"ecosystem":"Packagist","fixed":["10.4.10"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-q9cp-mc96-m4w2"},{"ecosystem":"Packagist","fixed":["10.4.10"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-q9cp-mc96-m4w2"},{"ecosystem":"Packagist","fixed":["10.4.10"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-q9cp-mc96-m4w2"}],"prev":{"headline":"Cleartext storage of session identifier","id":"CVE-2020-26228"},"products":["TYPO3.CMS"],"published":"2020-11-23","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":"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":"Authenticated backend users could exploit XML External Entity vulnerabilities in RSS widgets to read sensitive data, though default configurations mitigate this risk.","url":"https://insights.sbomify.com/CVE-2020-26229/"}