Security readout for executives and security teams
Plain-English summary
CVE-2021-32768 is a cross-site scripting flaw in TYPO3 CMS rich-text rendering. Malicious content may run script in visitors' browsers when displayed. Default exploitation generally needs a valid backend user account, but custom frontend plugins accepting and reflecting rich text may allow unauthenticated exploitation. The source bundle provides no evidence of active exploitation.
Executive priority
Prioritize remediation for public TYPO3 sites, especially those with frontend rich-text submission features or many backend users. This is not rated critical, but it can affect visitor trust, session security, and website integrity if abused.
Technical view
Affected TYPO3.CMS versions fail to properly parse, sanitize, and encode malicious rich-text content during frontend rendering. TypoScript HTMLparser defaults do not cover all dangerous HTML tag and attribute combinations. The issue is CWE-79 with CVSS 3.1 score 6.1, reflecting network reachability, low attack complexity, user interaction, changed scope, and limited confidentiality/integrity impact.
Likely exposure
Exposure applies to TYPO3.CMS 7.0.0-7.6.52, 8.0.0-8.7.41, 9.0.0-9.5.28, 10.0.0-10.4.18, and 11.0.0-11.3.1. Risk is higher where custom frontend plugins accept and reflect user-submitted rich-text content.
Exploitation context
The vulnerability is remotely reachable and low complexity, but user interaction is required. Default scenarios require a valid backend user account. Custom frontend rich-text submission paths may remove that authentication requirement. KEV is false, and the provided sources do not state active exploitation.
Researcher notes
Focus review on TYPO3 frontend rendering of rich-text content and TypoScript HTMLparser behavior. Default exploitation depends on backend access, but custom plugins can materially change exposure. Evidence is sufficient for affected versions and fixed releases, but not for active exploitation.
Mitigation direction
- Upgrade to TYPO3 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, or 11.3.2.
- Review vendor advisory guidance before applying compensating controls.
- Restrict who can create or edit rich-text content until upgraded.
- Audit custom frontend plugins that accept and reflect rich-text input.
- Validate rich-text handling through TYPO3-supported sanitization and rendering controls.
Validation and detection
- Inventory all TYPO3 CMS versions across production, staging, and legacy sites.
- Identify websites running the affected version ranges listed by TYPO3.
- Review custom frontend plugins for user-submitted rich-text reflection paths.
- Confirm backend authoring permissions are limited to trusted users.
- Verify upgraded instances report fixed TYPO3 versions after maintenance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-32768 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://typo3.org/security/advisory/typo3-core-sa-2021-013CVE reference · x_refsource_MISC
- https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-c5c9-8c6m-727vCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.