← Back
GHSA-22q7-cg4r-p9mx
Cross-Site Scripting (XSS) in typo3/cms-fluid (GHSA-22q7-cg4r-p9mx)
Summary
cross-site scripting in typo3/cms-fluid (GHSA-22q7-cg4r-p9mx). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `9.5.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-22q7-cg4r-p9mx** has been found in typo3/cms-fluid.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade typo3/cms-fluid to **9.5.4** or later.
If unsure, ask your IT team or search "typo3/cms-fluid GHSA-22q7-cg4r-p9mx" on the vendor's site.
GHSA-22q7-cg4r-p9mx (typo3/cms-fluid) — CWE-79 /
Patched: `9.5.4` — 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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in typo3/cms-fluid.
📍 Affected scope
typo3/cms-fluid — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **9.5.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'typo3/cms-fluid' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'typo3/cms-fluid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `typo3/cms-fluid` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade typo3/cms-fluid to 9.5.4ステージング環境で 9.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
typo3/cms-fluid
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.4"}]}]
References
- web https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-01-22-4.yaml
- web https://typo3.org/security/advisory/typo3-core-sa-2019-005
- web https://github.com/TYPO3-CMS/fluid/commit/1a65dcc4a8f17f61a8055c0fd46c324c44c9980d
- web https://github.com/TYPO3-CMS/fluid/commit/a40f468d1534a68cfce91ce2a8e2a1ff81db5cf5
- web https://github.com/TYPO3-CMS/fluid/compare/v8.7.22...v8.7.23
- web https://github.com/TYPO3-CMS/fluid/compare/v9.5.3...v9.5.4
- web https://github.com/advisories/GHSA-22q7-cg4r-p9mx