Cross-Site Scripting via Rich-Text Content
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
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de Composer | 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 |
| Paquete de Composer | 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 |
Referencias
- https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-c5c9-8c6m-727v
- https://github.com/TYPO3/typo3/security/advisories/GHSA-c5c9-8c6m-727v
- https://nvd.nist.gov/vuln/detail/CVE-2021-32768
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2021-32768.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2021-32768.yaml
- https://typo3.org/security/advisory/typo3-core-sa-2021-013
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Debilidad (CWE)
CWE-79- Plataforma
- Composer
- Paquete
typo3/cms, typo3/cms-core- Publicada
- 19.08.2021
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-c5c9-8c6m-727v - CC BY 4.0
Historial de vulnerabilidades: typo3/cms-core
Todas las vulnerabilidades publicadas de este paquete (Paquete de Composer), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 128
- Primera → última
- 09.2018 09.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 1
- Alta 35
- Media 84
- Baja 8
Divulgaciones por año
- 2018: 2
- 2019: 0
- 2020: 13
- 2021: 15
- 2022: 34
- 2023: 3
- 2024: 38
- 2025: 8
- 2026: 15
-
Cross-Site Scripting via Rich-Text Content esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.