{"items":[{"id":"NVI-00004134","kind":"vulnerability","title":"Broken Access Control in Form Framework","revision":4,"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-3vg7-jw9m-pc3f","CVE-2021-21357"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-0d713fa8a4e653411832469ede513a26"],"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.880Z","value":"6.5 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.880Z","value":"8.3 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.880Z","value":"8.3 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"1.606%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.75915. Missing scores are unknown.","source_id":"sr-0d713fa8a4e653411832469ede513a26"}],"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-596935cf5057d7e91a59c4c82fa46b6d","url":"https://github.com/advisories/GHSA-3vg7-jw9m-pc3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3vg7-jw9m-pc3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.660Z"},{"id":"sr-2b46efbb4318326574b1d40b867b7472","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21357","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21357","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"},{"id":"sr-0d713fa8a4e653411832469ede513a26","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-21357","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-11-06T00:29:57.250Z","source_updated_at":"2026-07-08T06:28:31.297Z","source_disclosed_at":"2021-03-23T01:53:57.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.660Z"},{"id":"NVI-00004134","kind":"vulnerability","title":"Broken Access Control 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-3vg7-jw9m-pc3f","CVE-2021-21357"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-991466ddd92d412b398f99498b32261e"],"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.880Z","value":"6.5 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.880Z","value":"8.3 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.880Z","value":"8.3 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.606%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.7589. Missing scores are unknown.","source_id":"sr-991466ddd92d412b398f99498b32261e"}],"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-596935cf5057d7e91a59c4c82fa46b6d","url":"https://github.com/advisories/GHSA-3vg7-jw9m-pc3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3vg7-jw9m-pc3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.660Z"},{"id":"sr-2b46efbb4318326574b1d40b867b7472","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21357","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21357","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"},{"id":"sr-991466ddd92d412b398f99498b32261e","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-21357","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-11-04T02:53:03.158Z","source_updated_at":"2026-07-08T06:28:31.297Z","source_disclosed_at":"2021-03-23T01:53:57.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.660Z"},{"id":"NVI-00004134","kind":"vulnerability","title":"Broken Access Control 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-3vg7-jw9m-pc3f","CVE-2021-21357"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-2b46efbb4318326574b1d40b867b7472"],"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.880Z","value":"6.5 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.880Z","value":"8.3 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"},{"kind":"CVSS","as_of":"2026-06-17T03:35:22.880Z","value":"8.3 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2b46efbb4318326574b1d40b867b7472"}],"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-596935cf5057d7e91a59c4c82fa46b6d","url":"https://github.com/advisories/GHSA-3vg7-jw9m-pc3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3vg7-jw9m-pc3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.660Z"},{"id":"sr-2b46efbb4318326574b1d40b867b7472","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21357","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21357","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-10-31T22:27:03.549Z","source_updated_at":"2026-07-08T06:28:31.297Z","source_disclosed_at":"2021-03-23T01:53:57.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.660Z"},{"id":"NVI-00004134","kind":"vulnerability","title":"Broken Access Control in Form Framework","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3vg7-jw9m-pc3f","CVE-2021-21357"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d"],"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-596935cf5057d7e91a59c4c82fa46b6d","url":"https://github.com/advisories/GHSA-3vg7-jw9m-pc3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3vg7-jw9m-pc3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.660Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.40"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.14"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.1.1"]},{"certainty":"source_listed","source_ids":["sr-596935cf5057d7e91a59c4c82fa46b6d"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"\n### Problem\nDue to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.\n\nIn the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.\n\nA valid backend user account with access to the form module is needed 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\n### Credits\nThanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.\n\n### References\n* TYPO3-CORE-SA-2021-003","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.25"]}],"null_published_at":"2026-10-31T22:12:52.629Z","source_updated_at":"2026-07-08T06:28:31.297Z","source_disclosed_at":"2021-03-23T01:53:57.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.660Z"}],"next_cursor":null,"snapshot_revision":"42594"}