SQL Injection in typo3/cms-core (CVE-2026-49741)
Summary
SQL injection in typo3/cms-core (CVE-2026-49741). Risk of unauthorized operations or information disclosure. Exploitable via form_definition. Mitigation: upgrade to 14.3.3 or later.
Original description
The description as published by the source.
Backend users with write access to the form_definition database table were able to directly create, update, or delete form definition records via DataHandler, bypassing the Form Framework's persistence validation and permission checks. This allowed injecting arbitrary form configurations, re-enabling attack vectors originally addressed in TYPO3-CORE-SA-2018-003, including SQL injection and privilege escalation. This issue affects TYPO3 CMS versions 14.0.0-14.3.2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2026-49741 has been found in typo3/cms-core.
Attackers can target a specific entry point like form_definition over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade typo3/cms-core to 14.3.3 or later.
If unsure, ask your IT team or search "typo3/cms-core CVE-2026-49741" on the vendor's site.
CVE-2026-49741 (typo3/cms-core) — CWE-89
Attack surface: form_definition / DataHandler
Patched: 14.3.3 — 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.
SQL injection (CWE-89) exists in typo3/cms-core. Attackers reach the vulnerable code path via form_definition.
Check the vendor advisory for the affected versions of typo3/cms-core. Attack surface: form_definition / DataHandler.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 14.3.3.
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 14.3.3ステージング環境で 14.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory typo3.org
- advisory typo3.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web packagist.org