{"items":[{"id":"NVI-00005224","kind":"vulnerability","title":"TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering","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-r4f8-f93x-5qh3","CVE-2023-24814"],"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 12.2.0 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.36 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.40 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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 8.7.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.35 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.2.0 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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-1e24dbfc10411a082618d48659fb9a03"],"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-17T05:39:54.917Z","value":"8.8 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7aaa8cbef79171d3637eaaa02f23f117"},{"kind":"CVSS","as_of":"2026-06-17T05:39:54.917Z","value":"6.1 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-7aaa8cbef79171d3637eaaa02f23f117"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.831%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.57606. Missing scores are unknown.","source_id":"sr-1e24dbfc10411a082618d48659fb9a03"}],"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-870d68861e6de5c76b82f9119947edf9","url":"https://github.com/advisories/GHSA-r4f8-f93x-5qh3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r4f8-f93x-5qh3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.356Z"},{"id":"sr-7aaa8cbef79171d3637eaaa02f23f117","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-24814","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-24814","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:29.087Z"},{"id":"sr-1e24dbfc10411a082618d48659fb9a03","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-2023-24814","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:14:50.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.36"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.40"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 8.7.0; fixed 8.7.51"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.35"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]}],"null_published_at":"2026-11-07T14:01:58.727Z","source_updated_at":"2026-09-10T03:49:52.186Z","source_disclosed_at":"2023-02-08T21:33:24.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:41.356Z"},{"id":"NVI-00005224","kind":"vulnerability","title":"TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering","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-r4f8-f93x-5qh3","CVE-2023-24814"],"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 12.2.0 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.36 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.40 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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 8.7.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.35 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.2.0 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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-425f669faeb75476df3b0ae66aec6324"],"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-17T05:39:54.917Z","value":"8.8 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7aaa8cbef79171d3637eaaa02f23f117"},{"kind":"CVSS","as_of":"2026-06-17T05:39:54.917Z","value":"6.1 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-7aaa8cbef79171d3637eaaa02f23f117"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.831%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.57615. Missing scores are unknown.","source_id":"sr-425f669faeb75476df3b0ae66aec6324"}],"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-870d68861e6de5c76b82f9119947edf9","url":"https://github.com/advisories/GHSA-r4f8-f93x-5qh3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r4f8-f93x-5qh3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.356Z"},{"id":"sr-7aaa8cbef79171d3637eaaa02f23f117","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-24814","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-24814","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:29.087Z"},{"id":"sr-425f669faeb75476df3b0ae66aec6324","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-2023-24814","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.36"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.40"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 8.7.0; fixed 8.7.51"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.35"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]}],"null_published_at":"2026-11-03T17:49:21.342Z","source_updated_at":"2026-09-10T03:49:52.186Z","source_disclosed_at":"2023-02-08T21:33:24.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:41.356Z"},{"id":"NVI-00005224","kind":"vulnerability","title":"TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-r4f8-f93x-5qh3","CVE-2023-24814"],"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 12.2.0 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.36 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.40 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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 8.7.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.35 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.2.0 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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-425f669faeb75476df3b0ae66aec6324"],"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.831%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.57615. Missing scores are unknown.","source_id":"sr-425f669faeb75476df3b0ae66aec6324"}],"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-870d68861e6de5c76b82f9119947edf9","url":"https://github.com/advisories/GHSA-r4f8-f93x-5qh3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r4f8-f93x-5qh3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.356Z"},{"id":"sr-425f669faeb75476df3b0ae66aec6324","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-2023-24814","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.36"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.40"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 8.7.0; fixed 8.7.51"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.35"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]}],"null_published_at":"2026-10-31T23:18:17.217Z","source_updated_at":"2026-09-10T03:49:52.186Z","source_disclosed_at":"2023-02-08T21:33:24.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:41.356Z"},{"id":"NVI-00005224","kind":"vulnerability","title":"TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-r4f8-f93x-5qh3","CVE-2023-24814"],"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 12.2.0 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.36 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.40 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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 8.7.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.35 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.23 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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.2.0 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"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-870d68861e6de5c76b82f9119947edf9","url":"https://github.com/advisories/GHSA-r4f8-f93x-5qh3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r4f8-f93x-5qh3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.356Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.36"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.40"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 8.7.0; fixed 8.7.51"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.35"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.23"]},{"certainty":"source_listed","source_ids":["sr-870d68861e6de5c76b82f9119947edf9"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C` (8.2)\n\n### Problem\nTYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content.\n\nIn combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code into pages that have not yet been rendered and cached. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting).\n\nIndividual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well.\n\n- `GeneralUtility::getIndpEnv('PATH_INFO') `\n- `GeneralUtility::getIndpEnv('SCRIPT_NAME') `\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')`\n- `GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')`\n- `GeneralUtility::getIndpEnv('TYPO3_SITE_PA","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.2.0"]}],"null_published_at":"2026-10-31T22:13:01.456Z","source_updated_at":"2026-09-10T03:49:52.186Z","source_disclosed_at":"2023-02-08T21:33:24.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:41.356Z"}],"next_cursor":null,"snapshot_revision":"42594"}