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 persisten…
Summary
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.
In-depth triage · Auto channel
No in-depth report has been generated yet (DR-003 v2 AI pipeline is under construction).
Lint boundary warnings (2)
The following non-blocking warnings were raised during the lint phase of this triage (e.g. reference URLs not yet on the allowlist). They do not affect entry usability and are disclosed for transparency (see DR-002).
-
REF_URL_NOT_ALLOWLISTEDurl not in allowlist: https://typo3.org/security/advisory/typo3-core-sa-2018-003 -
REF_URL_NOT_ALLOWLISTEDurl not in allowlist: https://typo3.org/security/advisory/typo3-core-sa-2026-017
Sources
- NVD DATABASE
Original Links
- https://github.com/TYPO3/typo3/commit/c90493c13b633f328cf2c066182c90a1655ff0fc
- https://typo3.org/security/advisory/typo3-core-sa-2018-003
- https://typo3.org/security/advisory/typo3-core-sa-2026-017
Timeline
- nvd_ingest NVD