← Back
CVE-2026-6553
Vulnerability in typo3/cms-backend (CVE-2026-6553)
Summary
vulnerability in typo3/cms-backend (CVE-2026-6553). Confidential information can be exposed externally. Exploitable via ``SetupModuleController``. Mitigation: upgrade to `14.3.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-6553** has been found in typo3/cms-backend.
Attackers can target a specific entry point like ``SetupModuleController`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade typo3/cms-backend to **14.3.0** or later.
If unsure, ask your IT team or search "typo3/cms-backend CVE-2026-6553" on the vendor's site.
CVE-2026-6553 (typo3/cms-backend) — CWE-312 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `SetupModuleController` / `user_settings` / `be_users`
Patched: `14.3.0` — 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
**A vulnerability** (CWE-312) exists in typo3/cms-backend. Attackers reach the vulnerable code path via ``SetupModuleController`` without authentication.
📍 Affected scope
typo3/cms-backend — . Attack surface: `SetupModuleController` / `user_settings` / `be_users`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **14.3.0**.
🛡️ 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-backend' .` 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-backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `typo3/cms-backend` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade typo3/cms-backend to 14.3.0ステージング環境で 14.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
typo3/cms-backend
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.3.0"}]}]
Packagist
typo3/cms-backend
[{"type":"ECOSYSTEM","events":[{"introduced":"14.2.0"},{"fixed":"14.3.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-6553
- package https://github.com/TYPO3/typo3
- web https://github.com/TYPO3/typo3/security/advisories/GHSA-xvv6-p4wf-mvx7
- web https://github.com/TYPO3/typo3/commit/9a6e913f70767f63b322ae3e2d2f4e302624c291
- web https://typo3.org/security/advisory/typo3-core-sa-2026-005
- web https://github.com/advisories/GHSA-xvv6-p4wf-mvx7