# CVE-2021-32768: Cross-Site Scripting via Rich-Text Content > Attackers can inject malicious scripts into TYPO3 frontend via rich-text content, potentially leading to code execution or account takeover. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 10 Aug 2021 - **Updated:** 3 Aug 2024 - **Also known as:** BIT-typo3-2021-32768, GHSA-c5c9-8c6m-727v ## What is CVE-2021-32768? CVE-2021-32768 is a medium-severity cross-site scripting vulnerability in Typo3 Typo3, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description TYPO3 is an open source PHP based web content management system released under the GNU GPL. In affected versions 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 does not consider all potentially malicious HTML tag & attribute combinations per default. 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. 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2021-32768? 21 open source packages ship an affected version, including typo3/cms, typo3 and typo3/cms-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/cms` | Packagist | From 10.0.0 | 10.4.19 | | `typo3/cms` | Packagist | From 10.0.0 | 10.4.19 | | `typo3/cms` | Packagist | From 11.0.0 | 11.3.2 | | `typo3/cms` | Packagist | From 11.0.0 | 11.3.2 | | `typo3/cms` | Packagist | From 7.0.0 | 7.6.53 | | `typo3/cms` | Packagist | From 7.0.0 | 7.6.53 | | `typo3/cms` | Packagist | From 8.0.0 | 8.7.42 | | `typo3/cms` | Packagist | From 8.0.0 | 8.7.42 | | `typo3/cms` | Packagist | From 9.0.0 | 9.5.29 | | `typo3/cms` | Packagist | From 9.0.0 | 9.5.29 | | `typo3` | Bitnami | From 7.0.0 | 7.6.52, 8.7.41, 9.5.28, 10.4.18, 11.3.1 | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.19 | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.19 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.3.2 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.3.2 | | `typo3/cms-core` | Packagist | From 7.0.0 | 7.6.53 | | `typo3/cms-core` | Packagist | From 7.0.0 | 7.6.53 | | `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.42 | | `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.42 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.29 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.29 | Products: Typo3 Typo3. ## How do I fix CVE-2021-32768? Upgrade typo3/cms to a fixed version for your release line: 10.4.19, 11.3.2, 7.6.53 or 8.7.42. ## Is CVE-2021-32768 being exploited? There is no known exploitation of CVE-2021-32768 in the wild and no public exploit code. ## Other vulnerabilities in Typo3 Typo3 - [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0) - [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8) - [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8) - [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8) - [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-32768 and fix it if it is affected. What it is: CVE-2021-32768 is a medium-severity cross-site scripting vulnerability in Typo3 Typo3, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2021-32768 in the wild and no public exploit code. Affected packages and fixed versions: - typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.19 - typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.19 - typo3/cms (Packagist): affected from 11.0.0; fixed in 11.3.2 - typo3/cms (Packagist): affected from 11.0.0; fixed in 11.3.2 - typo3/cms (Packagist): affected from 7.0.0; fixed in 7.6.53 - typo3/cms (Packagist): affected from 7.0.0; fixed in 7.6.53 - typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.42 - typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.42 - typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.29 - typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.29 - typo3 (Bitnami): affected from 7.0.0; fixed in 7.6.52, 8.7.41, 9.5.28, 10.4.18, 11.3.1 - typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.19 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2021-32768/ (Markdown: https://insights.sbomify.com/CVE-2021-32768/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32768 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32768 - OSV: https://osv.dev/vulnerability/CVE-2021-32768 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-32768/ Summaries are generated and may contain mistakes; the official description above is the record.