{"items":[{"id":"NVI-00007124","kind":"vulnerability","title":"Cross-Site Scripting via Rich-Text Content","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-c5c9-8c6m-727v","CVE-2021-32768"],"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 7.6.53 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.42 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.19 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.3.2 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.29 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.19 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.3.2 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.29 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.42 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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 7.6.53 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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-06edf3a8a444db8d1aedef389db7801e"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T03:53:35.440Z","value":"4.3 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-802de833214ebdf55c6b2f52f99d3cb9"},{"kind":"CVSS","as_of":"2026-06-17T03:53:35.440Z","value":"6.1 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-802de833214ebdf55c6b2f52f99d3cb9"},{"kind":"CVSS","as_of":"2026-06-17T03:53:35.440Z","value":"6.1 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-802de833214ebdf55c6b2f52f99d3cb9"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.727%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.54164. Missing scores are unknown.","source_id":"sr-06edf3a8a444db8d1aedef389db7801e"}],"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-cfa3e4550d9d8ff3263c4b35fd30d2e1","url":"https://github.com/advisories/GHSA-c5c9-8c6m-727v","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c5c9-8c6m-727v","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.695Z"},{"id":"sr-802de833214ebdf55c6b2f52f99d3cb9","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-32768","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-32768","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:13:26.837Z"},{"id":"sr-06edf3a8a444db8d1aedef389db7801e","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-32768","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.53"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.42"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.19"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.3.2"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.29"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.19"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.3.2"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.29"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.42"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.53"]}],"null_published_at":"2026-11-03T17:49:21.351Z","source_updated_at":"2026-07-08T06:29:25.329Z","source_disclosed_at":"2021-08-19T15:53:12.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-00007124","kind":"vulnerability","title":"Cross-Site Scripting via Rich-Text Content","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c5c9-8c6m-727v","CVE-2021-32768"],"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 7.6.53 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.42 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.19 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.3.2 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.29 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.19 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.3.2 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.29 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.42 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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 7.6.53 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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-06edf3a8a444db8d1aedef389db7801e"],"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-11-01T12:00:16.000Z","value":"0.727%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.54164. Missing scores are unknown.","source_id":"sr-06edf3a8a444db8d1aedef389db7801e"}],"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-cfa3e4550d9d8ff3263c4b35fd30d2e1","url":"https://github.com/advisories/GHSA-c5c9-8c6m-727v","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c5c9-8c6m-727v","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.695Z"},{"id":"sr-06edf3a8a444db8d1aedef389db7801e","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-32768","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.53"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.42"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.19"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.3.2"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.29"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.19"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.3.2"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.29"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.42"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.53"]}],"null_published_at":"2026-11-02T20:21:07.826Z","source_updated_at":"2026-07-08T06:29:25.329Z","source_disclosed_at":"2021-08-19T15:53:12.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-00007124","kind":"vulnerability","title":"Cross-Site Scripting via Rich-Text Content","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c5c9-8c6m-727v","CVE-2021-32768"],"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 7.6.53 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.42 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.19 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.3.2 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.29 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.19 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.3.2 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.29 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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.42 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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 7.6.53 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"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-cfa3e4550d9d8ff3263c4b35fd30d2e1","url":"https://github.com/advisories/GHSA-c5c9-8c6m-727v","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-c5c9-8c6m-727v","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.695Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.53"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.42"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.19"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.3.2"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.29"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 10.0.0; fixed 10.4.19"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.3.2"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 9.0.0; fixed 9.5.29"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.7.42"]},{"certainty":"source_listed","source_ids":["sr-cfa3e4550d9d8ff3263c4b35fd30d2e1"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"> ### Meta\n> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)\n\n### Problem\nFailing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _HTMLparser_ do not consider all potentially malicious HTML tag & attribute combinations per default.\n\nIn addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.\n\nIn default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.\n\n### Solution\nUpdate to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.\n\nCustom package _typo3/html-sanitizer_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. T","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.6.53"]}],"null_published_at":"2026-10-31T22:13:14.313Z","source_updated_at":"2026-07-08T06:29:25.329Z","source_disclosed_at":"2021-08-19T15:53:12.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":"40769"}