Cross-Site Scripting (XSS) in typo3/cms-core (CVE-2021-32668)
Summary
Cross-site scripting in typo3/cms-core (CVE-2021-32668). Confidential information can be exposed externally. Mitigation: upgrade to 11.3.1 or later.
Original description
The description as published by the source.
Meta
- CVSS:
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C(4.5)
Problem
Failing to properly encode error messages, the components QueryGenerator and QueryView are vulnerable to both reflected and persistent cross-site scripting. A valid backend user account having administrator privileges is needed to exploit this vulnerability.
Solution
Update to TYPO3 versions 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.
Credits
Thanks to Richie Lee who reported this issue and to TYPO3 security team member Oliver Hader who fixed the issue.
References
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32668 has been found in typo3/cms-core.
Confidential information can be exposed externally.
What to do: upgrade typo3/cms-core to 11.3.1 or later.
If unsure, ask your IT team or search "typo3/cms-core CVE-2021-32668" on the vendor's site.
CVE-2021-32668 (typo3/cms-core) — CWE-79
Attack vector: remote (network-reachable)
Patched: 11.3.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in typo3/cms-core.
Check the vendor advisory for the affected versions of typo3/cms-core.
Severity: ?. Confidential information can be exposed externally.
Update to 11.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'typo3/cms-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'typo3/cms-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
typo3/cms-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade typo3/cms-core to 11.3.1ステージング環境で 11.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web typo3.org