Cross-Site Scripting (XSS) in typo3/cms-core (CVE-2020-11065)
Summary
Cross-site scripting in typo3/cms-core (CVE-2020-11065). Risk of unauthorized operations or information disclosure. Exploitable via typolink. Mitigation: upgrade to 9.5.17 or later.
Original description
The description as published by the source.
It has been discovered that link tags generated by typolink functionality are vulnerable to cross-site scripting - properties being assigned as HTML attributes have not been parsed correctly.
Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.
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-2020-11065 has been found in typo3/cms-core.
Attackers can target a specific entry point like typolink over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade typo3/cms-core to 9.5.17 or later.
If unsure, ask your IT team or search "typo3/cms-core CVE-2020-11065" on the vendor's site.
CVE-2020-11065 (typo3/cms-core) — CWE-79
Attack vector: remote (network-reachable)
Attack surface: typolink
Patched: 9.5.17 — 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. Attackers reach the vulnerable code path via typolink.
Check the vendor advisory for the affected versions of typo3/cms-core. Attack surface: typolink.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 9.5.17.
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 9.5.17ステージング環境で 9.5.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web typo3.org