{"items":[{"id":"NVI-00002701","kind":"vulnerability","title":"TYPO3 CMS has Broken Access Control in its 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-hwvq-2w67-rvxp","CVE-2026-47346"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 10.4.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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.57 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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-337d9d482fd59799b05cd5dc72e0de48"],"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-07-23T08:10:00.137Z","value":"7.6 HIGH (4.0)","meaning":"f4fb688c-4412-4426-b4b8-421ecf27b14a severity; no combined Null risk score.","source_id":"sr-5a7f2f18d8b479d4ba8a9216af4364d0"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.253%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.16785. Missing scores are unknown.","source_id":"sr-337d9d482fd59799b05cd5dc72e0de48"}],"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-234bc0addacf7ce43f161280439eda40","url":"https://github.com/advisories/GHSA-hwvq-2w67-rvxp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hwvq-2w67-rvxp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.433Z"},{"id":"sr-5a7f2f18d8b479d4ba8a9216af4364d0","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-47346","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-47346","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-337d9d482fd59799b05cd5dc72e0de48","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-2026-47346","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.280Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]}],"null_published_at":"2026-11-07T18:43:12.118Z","source_updated_at":"2026-09-10T03:50:49.888Z","source_disclosed_at":"2026-06-12T19:32:09.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.433Z"},{"id":"NVI-00002701","kind":"vulnerability","title":"TYPO3 CMS has Broken Access Control in its 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-hwvq-2w67-rvxp","CVE-2026-47346"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 10.4.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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.57 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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-3da5670f7ff6ac573656ef566b363130"],"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-07-23T08:10:00.137Z","value":"7.6 HIGH (4.0)","meaning":"f4fb688c-4412-4426-b4b8-421ecf27b14a severity; no combined Null risk score.","source_id":"sr-5a7f2f18d8b479d4ba8a9216af4364d0"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.253%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.16791. Missing scores are unknown.","source_id":"sr-3da5670f7ff6ac573656ef566b363130"}],"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-234bc0addacf7ce43f161280439eda40","url":"https://github.com/advisories/GHSA-hwvq-2w67-rvxp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hwvq-2w67-rvxp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.433Z"},{"id":"sr-5a7f2f18d8b479d4ba8a9216af4364d0","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-47346","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-47346","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-3da5670f7ff6ac573656ef566b363130","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-2026-47346","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]}],"null_published_at":"2026-11-02T20:21:10.269Z","source_updated_at":"2026-09-10T03:50:49.888Z","source_disclosed_at":"2026-06-12T19:32:09.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:20.433Z"},{"id":"NVI-00002701","kind":"vulnerability","title":"TYPO3 CMS has Broken Access Control in its Form Framework","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hwvq-2w67-rvxp","CVE-2026-47346"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 10.4.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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.57 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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-3da5670f7ff6ac573656ef566b363130"],"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":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.253%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.16791. Missing scores are unknown.","source_id":"sr-3da5670f7ff6ac573656ef566b363130"}],"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-234bc0addacf7ce43f161280439eda40","url":"https://github.com/advisories/GHSA-hwvq-2w67-rvxp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hwvq-2w67-rvxp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.433Z"},{"id":"sr-3da5670f7ff6ac573656ef566b363130","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-2026-47346","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]}],"null_published_at":"2026-10-31T23:18:17.193Z","source_updated_at":"2026-09-10T03:50:49.888Z","source_disclosed_at":"2026-06-12T19:32:09.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.433Z"},{"id":"NVI-00002701","kind":"vulnerability","title":"TYPO3 CMS has Broken Access Control in its Form Framework","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hwvq-2w67-rvxp","CVE-2026-47346"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 10.4.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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.57 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.4.46 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 13.4.31 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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 14.3.3 for typo3/cms-form. Confirm the publisher’s latest guidance.","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"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-234bc0addacf7ce43f161280439eda40","url":"https://github.com/advisories/GHSA-hwvq-2w67-rvxp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hwvq-2w67-rvxp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.433Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-234bc0addacf7ce43f161280439eda40"],"technology":"typo3/cms-form","known_exclusions":[],"conditions_summary":"### Problem\nBackend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., `.FORM.YAML`) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-008","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]}],"null_published_at":"2026-10-31T22:00:33.901Z","source_updated_at":"2026-09-10T03:50:49.888Z","source_disclosed_at":"2026-06-12T19:32:09.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:20.433Z"}],"next_cursor":null,"snapshot_revision":"42594"}