{"items":[{"id":"NVI-00002987","kind":"vulnerability","title":"TYPO3 vulnerable to Improper Access Control Persisting File Abstraction Layer Entities via Data Handler","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-rj3x-wvc6-5j66","CVE-2024-25121"],"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 8.7.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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 9.5.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.43 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.35 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.11 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.0.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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-97e566075b0fbb9a65c0506fbee5bf8e"],"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-17T07:15:32.823Z","value":"7.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-97e566075b0fbb9a65c0506fbee5bf8e"},{"kind":"CVSS","as_of":"2026-06-17T07:15:32.823Z","value":"7.1 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-97e566075b0fbb9a65c0506fbee5bf8e"}],"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-2e0b565a1d30cc1c8ee1e11c2da5ed16","url":"https://github.com/advisories/GHSA-rj3x-wvc6-5j66","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rj3x-wvc6-5j66","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.363Z"},{"id":"sr-97e566075b0fbb9a65c0506fbee5bf8e","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-25121","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-25121","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:14.650Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.57"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.46"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.43"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.35"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.11"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.0.1"]}],"null_published_at":"2026-11-04T18:04:07.067Z","source_updated_at":"2026-09-10T03:50:09.956Z","source_disclosed_at":"2024-02-13T17:29:03.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:41.363Z"},{"id":"NVI-00002987","kind":"vulnerability","title":"TYPO3 vulnerable to Improper Access Control Persisting File Abstraction Layer Entities via Data Handler","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rj3x-wvc6-5j66","CVE-2024-25121"],"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 8.7.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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 9.5.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.43 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.35 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.11 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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.0.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"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-2e0b565a1d30cc1c8ee1e11c2da5ed16","url":"https://github.com/advisories/GHSA-rj3x-wvc6-5j66","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rj3x-wvc6-5j66","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.363Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.57"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.46"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.43"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.35"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.11"]},{"certainty":"source_listed","source_ids":["sr-2e0b565a1d30cc1c8ee1e11c2da5ed16"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nEntities of the File Abstraction Layer (FAL) could be persisted directly via `DataHandler`. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage (\"zero-storage\") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.\n\n\n### Solution\nUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.\n\n#### ℹ️ Strong security defaults - Manual actions required\n\nWhen persisting entities of the File Abstraction Layer directly via DataHandler, `sys_file` entities are now denied by default, and `sys_file_reference` & `sys_file_metadata` entities are not permitted to reference files in the fallback storage anymore.\n\nWhen importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using `$dataHandler->isImporting = true;`.\n\n### Credits\nThanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.\n","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.0.1"]}],"null_published_at":"2026-10-31T22:12:38.464Z","source_updated_at":"2026-09-10T03:50:09.956Z","source_disclosed_at":"2024-02-13T17:29:03.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:41.363Z"}],"next_cursor":null,"snapshot_revision":"42594"}