Medium

Cross-Site Scripting via Rich-Text Content

  • Disclosed: 19.08.2021
  • Updated: 11.10.2026 10:22

Meta

  • 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)

Problem

Failing 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.

In addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.

In 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.

Solution

Update 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.

Custom package typo3/html-sanitizer - based on allow-lists only - takes care of sanitizing potentially malicious markup. The default behavior is based on safe and commonly used markup - however, this can be extended or restricted further in case it is necessary for individual scenarios.

During the frontend rendering process, sanitization is applied to the default TypoScript path lib.parseFunc, which is implicitly used by the Fluid view-helper instruction f:format.html. Rich-text data persisted using the backend user interface is sanitized as well. Implementation details are explained in corresponding ChangeLog documentation.

Credits

Thanks to Benjamin Stiber, Gert-Jan Jansma, Gábor Ács-Kurucz, Alexander Kellner, Richie Lee, Nina Rösch who reported this issue, and to TYPO3 security team member Oliver Hader, as well as TYPO3 contributor Susanne Moog who fixed the issue.

References

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package typo3/cms >= 10.0.0, < 10.4.19, >= 11.0.0, < 11.3.2, >= 9.0.0, < 9.5.29, >= 8.0.0, < 8.7.42, >= 7.0.0, < 7.6.53 10.4.19, 11.3.2, 9.5.29, 8.7.42, 7.6.53
Composer package typo3/cms-core >= 7.0.0, < 7.6.53, >= 8.0.0, < 8.7.42, >= 10.0.0, < 10.4.19, >= 11.0.0, < 11.3.2, >= 9.0.0, < 9.5.29 7.6.53, 8.7.42, 10.4.19, 11.3.2, 9.5.29

References

CVSS score 6.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weakness (CWE)
CWE-79
Platform
Composer
Package
typo3/cms, typo3/cms-core
Disclosed
19.08.2021
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-c5c9-8c6m-727v - CC BY 4.0

Vulnerability history: typo3/cms

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (188) in the archive
Total entries
188
First → latest
09.2018 06.2024
Without a fix
3
Exploited in attacks
0

Severity breakdown

  • Critical 6
  • High 41
  • Medium 128
  • Low 13

Disclosures per year

  1. 2018: 2
  2. 2019: 0
  3. 2020: 13
  4. 2021: 15
  5. 2022: 85
  6. 2023: 1
  7. 2024: 72
  8. 2025: 0
  9. 2026: 0
Severity:
  1. High · 8.1 ghsa-f777-f784-36gm >= 7.0.0, < 7.6.32, >= 8.0.0, < 8.7.21, >= 9.0.0, < 9.5.2 7.6.32, 8.7.21, 9.5.2
  2. High · 8.8 ghsa-8h4m-r4wm-xj7r >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  3. High · 7.5 ghsa-g585-crjf-vhwq >= 7.0.0, < 7.6.32, >= 8.0.0, < 8.7.21 7.6.32, 8.7.21
  4. High · 7.3 ghsa-c5mj-39cf-3pp5 >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  5. High · 8.1 ghsa-hh95-5xm5-v8v7 >= 8.0.0, < 8.7.30, >= 9.0.0, < 9.5.12 8.7.30, 9.5.12
  6. High ghsa-ppgf-8745-8pgx >= 7.0.0, < 7.6.30, >= 8.0.0, < 8.7.17, >= 9.0.0, < 9.3.2 7.6.30, 8.7.17, 9.3.2
  7. High · 8.8 ghsa-7qwg-fcpw-xg5g >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  8. High ghsa-g4pf-3jvq-2gcw >= 6.2.0, < 6.2.30, >= 7.6.0, < 7.6.15, >= 8.0.0, < 8.5.1 6.2.30, 7.6.15, 8.5.1
  9. Critical · 9.9 ghsa-67wg-6j7r-mqh8 >= 7.6.0, < 7.6.22, >= 8.0.0, < 8.7.5 7.6.22, 8.7.5
  10. High ghsa-8h28-f46f-m87h >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  11. Critical · 9.0 ghsa-gwfx-p7mr-f92v >= 6.2.0, < 6.2.25, >= 7.6.0, < 7.6.8, >= 8.0.0, < 8.1.1 6.2.25, 7.6.8, 8.1.1
  12. High ghsa-qffc-gwpp-m2xr >= 6.2.0, < 6.2.19, >= 7.6.0, < 7.6.4 6.2.19, 7.6.4
  13. High ghsa-9895-53fc-98v2 >= 6.2.0, < 6.2.18 6.2.18
  14. High · 7.1 ghsa-r9vc-jfmh-6j48 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  15. High · 8.8 ghsa-4r76-xr68-w7m7 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  16. High ghsa-p84g-j2gh-83g3 >= 6.2.0, < 6.2.9, >= 7.0.0, < 7.0.2 6.2.9, 7.0.2
  17. High · 8.1 ghsa-45xg-4w5x-j429 >= 6.2.0, < 6.2.6, >= 6.1.0, < 6.1.12, >= 4.7.0, < 4.7.20, >= 4.5.0, < 4.5.37 6.2.6, 6.1.12, 4.7.20, 4.5.37
  18. High · 8.8 CVE-2023-24814 >= 10.0.0, < 10.4.35, >= 11.0.0, < 11.5.23, >= 12.0.0, < 12.2.0 10.4.35, 11.5.23, 12.2.0
  19. Critical · 9.8 CVE-2022-47406 < 2.0.5, >= 3.0.0, < 3.0.3 2.0.5, 3.0.3
  20. High · 7.5 CVE-2022-23503 >= 10.0.0, < 10.4.33, >= 11.0.0, < 11.5.20, >= 12.0.0, < 12.1.1 10.4.33, 11.5.20, 12.1.1
  21. High · 8.8 CVE-2019-12747 >= 8.0.0, < 8.7.27, >= 9.0.0, < 9.5.8 8.7.27, 9.5.8
  22. High · 7.5 CVE-2019-11832 >= 8.0.0, < 8.7.25, >= 9.0.0, < 9.5.6 8.7.25, 9.5.6
  23. High · 8.8 CVE-2019-19849 >= 10.0.0, < 10.2.1, >= 8.0.0, < 8.7.30, >= 9.0.0, < 9.5.12 10.2.1, 8.7.30, 9.5.12
  24. High CVE-2010-3714 >= 4.2.0, < 4.2.15, >= 4.3.0, < 4.3.7, >= 4.4.0, < 4.4.4 4.2.15, 4.3.7, 4.4.4
  25. High CVE-2013-4321 >= 6.0.0, < 6.0.9, >= 6.1.0, < 6.1.4 6.0.9, 6.1.4
  26. High CVE-2013-4250 >= 6.0.0, < 6.0.8, >= 6.1.0, < 6.1.3 6.0.8, 6.1.3
  27. High CVE-2014-9509 >= 4.5.0, < 4.5.39, >= 6.2.0, < 6.2.9, >= 7.0.0, < 7.0.2, >= 4.6.0, < 4.6.19, >= 4.7.0, < 4.7.21, >= 6.0.0, < 6.0.15, >= 6.1.0, < 6.1.13 4.5.39, 6.2.9, 7.0.2, 4.6.19, 4.7.21, 6.0.15, 6.1.13
  28. High CVE-2013-4701 >= 6.2.0, < 6.2.6 6.2.6
  29. High · 8.8 CVE-2017-14251 >= 7.6.0, < 7.6.22, >= 8.0.0, < 8.7.5 7.6.22, 8.7.5
  30. High CVE-2014-3942 >= 4.5.0, < 4.5.34, >= 4.7.0, < 4.7.19, >= 6.0.0, < 6.0.14, >= 6.1.0, < 6.1.9 4.5.34, 4.7.19, 6.0.14, 6.1.9
  31. High CVE-2010-1153 >= 4.3.0, < 4.3.3 4.3.3
  32. High CVE-2009-0258 >= 4.0.0, < 4.0.10, >= 4.1.0, < 4.1.8, >= 4.2.0, < 4.2.4 4.0.10, 4.1.8, 4.2.4
  33. High CVE-2009-0256 >= 4.0.0, < 4.0.10, >= 4.1.0, < 4.1.8, >= 4.2.0, < 4.2.4 4.0.10, 4.1.8, 4.2.4
  34. Critical · 9.8 CVE-2011-3583 >= 4.5.0, <= 4.5.5 no fix
  35. Critical · 9.8 CVE-2011-4628 < 4.3.12, >= 4.4.0, < 4.4.9, >= 4.5.0, < 4.5.4 4.3.12, 4.4.9, 4.5.4
  36. High · 8.8 CVE-2021-41113 >= 11.2.0, < 11.5.0 11.5.0
  37. Cross-Site Scripting via Rich-Text Content this entry
    Medium · 6.1 CVE-2021-32768 >= 10.0.0, < 10.4.19, >= 11.0.0, < 11.3.2, >= 9.0.0, < 9.5.29, >= 8.0.0, < 8.7.42, >= 7.0.0, < 7.6.53 10.4.19, 11.3.2, 9.5.29, 8.7.42, 7.6.53
  38. High · 8.3 CVE-2021-21357 >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1, >= 9.0.0, < 9.5.25 10.4.14, 11.1.1, 9.5.25
Show more (8) Showing 40 of 48

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.