TYPO3 CMS has Privilege Escalation & SQL Injection in its Form Framework
Published 12 Jun 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- >=14.0.0 <14.3.3
- Fixed in
- 14.3.3
composer require typo3/cms-core:^14.3.3- Affected
- >=14.0.0 <14.3.3
- Fixed in
- 14.3.3
composer require typo3/cms-form:^14.3.3Details
Problem
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.
Solution
Update to TYPO3 version 14.3.3 LTS that fixes the problem described.
Credits
TYPO3 CMS thanks Selçuk Güney for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.
Resources
Is GHSA-jh32-v29g-68pq in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-jh32-v29g-68pq
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-49741
- Linkgithub.com/TYPO3/typo3/commit/c90493c13b633f328cf2c066182c90a1655ff0fc
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-49741.yaml
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2018-003
- Linktypo3.org/security/advisory/typo3-core-sa-2026-017
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.