{"items":[{"id":"NVI-00006657","kind":"vulnerability","title":"Unrestricted File Upload in Form Framework","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-2r6j-862c-m2v2","CVE-2021-21355"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-form, typo3/cms-form, typo3/cms-form, typo3/cms-form, 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.40 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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-0741fb5baeae741e8d8f120348f46f33"],"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-17T03:35:22.740Z","value":"7.5 HIGH (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-04f19f07d8e696b9675f39ce6fdfb09a"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.740Z","value":"8.6 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-04f19f07d8e696b9675f39ce6fdfb09a"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.740Z","value":"8.6 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-04f19f07d8e696b9675f39ce6fdfb09a"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"1.631%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.7624. Missing scores are unknown.","source_id":"sr-0741fb5baeae741e8d8f120348f46f33"}],"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-bd7f6ceacd86f69ffb3371da57e2bf5b","url":"https://github.com/advisories/GHSA-2r6j-862c-m2v2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2r6j-862c-m2v2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.644Z"},{"id":"sr-04f19f07d8e696b9675f39ce6fdfb09a","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21355","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21355","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"},{"id":"sr-0741fb5baeae741e8d8f120348f46f33","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-2021-21355","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-11-02T20:21:07.827Z","source_updated_at":"2026-07-08T06:29:29.299Z","source_disclosed_at":"2021-03-23T01:53:52.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:41:49.644Z"},{"id":"NVI-00006657","kind":"vulnerability","title":"Unrestricted File Upload in Form Framework","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-2r6j-862c-m2v2","CVE-2021-21355"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-form, typo3/cms-form, typo3/cms-form, typo3/cms-form, 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.40 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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-04f19f07d8e696b9675f39ce6fdfb09a"],"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-17T03:35:22.740Z","value":"7.5 HIGH (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-04f19f07d8e696b9675f39ce6fdfb09a"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.740Z","value":"8.6 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-04f19f07d8e696b9675f39ce6fdfb09a"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.740Z","value":"8.6 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-04f19f07d8e696b9675f39ce6fdfb09a"}],"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-bd7f6ceacd86f69ffb3371da57e2bf5b","url":"https://github.com/advisories/GHSA-2r6j-862c-m2v2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2r6j-862c-m2v2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.644Z"},{"id":"sr-04f19f07d8e696b9675f39ce6fdfb09a","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21355","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21355","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-10-31T22:27:03.528Z","source_updated_at":"2026-07-08T06:29:29.299Z","source_disclosed_at":"2021-03-23T01:53:52.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:41:49.644Z"},{"id":"NVI-00006657","kind":"vulnerability","title":"Unrestricted File Upload in Form Framework","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2r6j-862c-m2v2","CVE-2021-21355"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-form, typo3/cms-form, typo3/cms-form, typo3/cms-form, 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.40 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.14 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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.25 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"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-bd7f6ceacd86f69ffb3371da57e2bf5b","url":"https://github.com/advisories/GHSA-2r6j-862c-m2v2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2r6j-862c-m2v2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.644Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-bd7f6ceacd86f69ffb3371da57e2bf5b"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.\n\nTYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.\n\nIn any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.\n\nNo authentication is required to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.\n\nType converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uplo","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-10-31T22:13:10.067Z","source_updated_at":"2026-07-08T06:29:29.299Z","source_disclosed_at":"2021-03-23T01:53:52.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:41:49.644Z"}],"next_cursor":null,"snapshot_revision":"42594"}