{"items":[{"id":"NVI-00004846","kind":"vulnerability","title":"TYPO3 Allows Unrestricted File Upload in File Abstraction Layer","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-9hq9-cr36-4wpj","CVE-2025-47939"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 9.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.50 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.44 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.12 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-c7633439bf7aac0852aab51a23fbc00f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T09:28:52.143Z","value":"5.4 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7666a6e615b01ce5dd64dab7c4653236"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.181%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.07702. Missing scores are unknown.","source_id":"sr-c7633439bf7aac0852aab51a23fbc00f"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-75f690e995d06c2a3e66ede2e29eacf9","url":"https://github.com/advisories/GHSA-9hq9-cr36-4wpj","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9hq9-cr36-4wpj","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.687Z"},{"id":"sr-7666a6e615b01ce5dd64dab7c4653236","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-47939","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2025-47939","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:14.276Z"},{"id":"sr-c7633439bf7aac0852aab51a23fbc00f","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2025-47939","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.371Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.51"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.50"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.44"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.31"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.12"]}],"null_published_at":"2026-11-06T21:03:48.025Z","source_updated_at":"2025-05-20T20:27:17.097Z","source_disclosed_at":"2025-05-20T19:35:21.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:10.687Z"},{"id":"NVI-00004846","kind":"vulnerability","title":"TYPO3 Allows Unrestricted File Upload in File Abstraction Layer","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-9hq9-cr36-4wpj","CVE-2025-47939"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 9.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.50 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.44 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.12 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-7666a6e615b01ce5dd64dab7c4653236"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T09:28:52.143Z","value":"5.4 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7666a6e615b01ce5dd64dab7c4653236"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-75f690e995d06c2a3e66ede2e29eacf9","url":"https://github.com/advisories/GHSA-9hq9-cr36-4wpj","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9hq9-cr36-4wpj","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.687Z"},{"id":"sr-7666a6e615b01ce5dd64dab7c4653236","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-47939","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2025-47939","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:14.276Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.51"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.50"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.44"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.31"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.12"]}],"null_published_at":"2026-11-03T17:49:18.513Z","source_updated_at":"2025-05-20T20:27:17.097Z","source_disclosed_at":"2025-05-20T19:35:21.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:10.687Z"},{"id":"NVI-00004846","kind":"vulnerability","title":"TYPO3 Allows Unrestricted File Upload in File Abstraction Layer","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9hq9-cr36-4wpj","CVE-2025-47939"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 9.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 10.4.50 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.44 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.12 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-75f690e995d06c2a3e66ede2e29eacf9","url":"https://github.com/advisories/GHSA-9hq9-cr36-4wpj","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9hq9-cr36-4wpj","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.687Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.51"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.50"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.44"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.31"]},{"certainty":"source_listed","source_ids":["sr-75f690e995d06c2a3e66ede2e29eacf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBy design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).\n\nAlthough such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site.\n\n### Solution\nUpdate to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.\n\n> [!NOTE]\n> The mitigation strategies outlined below apply broadly to all file uploads handled through TYPO3's File Abstraction Layer (FAL), ","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.12"]}],"null_published_at":"2026-10-31T22:12:57.145Z","source_updated_at":"2025-05-20T20:27:17.097Z","source_disclosed_at":"2025-05-20T19:35:21.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:10.687Z"}],"next_cursor":null,"snapshot_revision":"42594"}