{"items":[{"id":"NVI-00004237","kind":"vulnerability","title":"TYPO3 CMS vulnerable to Arbitrary Code Execution via 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-c5wx-6c2c-f7rm","CVE-2022-23503"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.49 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.38 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.33 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.33 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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-c997f1ba7c8c4ca1e47fc9afbce2af27"],"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-17T04:30:15.153Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-374b6225a536e4187d6f4735274608b4"},{"kind":"CVSS","as_of":"2026-06-17T04:30:15.153Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-374b6225a536e4187d6f4735274608b4"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.837%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.57762. Missing scores are unknown.","source_id":"sr-c997f1ba7c8c4ca1e47fc9afbce2af27"}],"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-5e5f1d76912887e78a12953c24a0e97f","url":"https://github.com/advisories/GHSA-c5wx-6c2c-f7rm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c5wx-6c2c-f7rm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.695Z"},{"id":"sr-374b6225a536e4187d6f4735274608b4","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-23503","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-23503","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:19.043Z"},{"id":"sr-c997f1ba7c8c4ca1e47fc9afbce2af27","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-2022-23503","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.49"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.38"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]}],"null_published_at":"2026-11-06T21:03:48.029Z","source_updated_at":"2023-12-06T01:01:58.903Z","source_disclosed_at":"2022-12-13T17:11:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:10.695Z"},{"id":"NVI-00004237","kind":"vulnerability","title":"TYPO3 CMS vulnerable to Arbitrary Code Execution via 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-c5wx-6c2c-f7rm","CVE-2022-23503"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.49 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.38 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.33 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.33 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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-374b6225a536e4187d6f4735274608b4"],"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-17T04:30:15.153Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-374b6225a536e4187d6f4735274608b4"},{"kind":"CVSS","as_of":"2026-06-17T04:30:15.153Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-374b6225a536e4187d6f4735274608b4"}],"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-5e5f1d76912887e78a12953c24a0e97f","url":"https://github.com/advisories/GHSA-c5wx-6c2c-f7rm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c5wx-6c2c-f7rm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.695Z"},{"id":"sr-374b6225a536e4187d6f4735274608b4","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-23503","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-23503","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:19.043Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.49"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.38"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]}],"null_published_at":"2026-11-01T01:04:01.281Z","source_updated_at":"2023-12-06T01:01:58.903Z","source_disclosed_at":"2022-12-13T17:11:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:10.695Z"},{"id":"NVI-00004237","kind":"vulnerability","title":"TYPO3 CMS vulnerable to Arbitrary Code Execution via Form Framework","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c5wx-6c2c-f7rm","CVE-2022-23503"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.7.49 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.38 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.33 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.20 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.1.1 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.33 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.20 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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.1.1 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"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-5e5f1d76912887e78a12953c24a0e97f","url":"https://github.com/advisories/GHSA-c5wx-6c2c-f7rm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c5wx-6c2c-f7rm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.695Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.49"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.38"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.33"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.20"]},{"certainty":"source_listed","source_ids":["sr-5e5f1d76912887e78a12953c24a0e97f"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Problem\nDue to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.\n\nThe existence of individual TypoScript instructions for a particular form item (known as `formDefinitionOverrides`) and a valid backend user account with access to the form module are needed to exploit this vulnerability.\n\n### Solution\nUpdate to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.\n\n### References\n* TYPO3-CORE-SA-2022-015\n","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.1.1"]}],"null_published_at":"2026-10-31T22:12:52.635Z","source_updated_at":"2023-12-06T01:01:58.903Z","source_disclosed_at":"2022-12-13T17:11:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:10.695Z"}],"next_cursor":null,"snapshot_revision":"42594"}