~ / search / GHSA-pjpj-v387-x4vq

GHSA-pjpj-v387-x4vq

TYPO3 CMS has Broken Access Control in its Form Framework

Source: GitHub Advisory Database (reviewed) High CVE-2026-11607

Packages

EcosystemPackageAffectedFixed in
Packagist typo3/cms-core < 10.4.57 10.4.57
Packagist typo3/cms-core >= 11.0.0, < 11.5.51 11.5.51
Packagist typo3/cms-core >= 12.0.0, < 12.4.46 12.4.46
Packagist typo3/cms-core >= 13.0.0, < 13.4.31 13.4.31
Packagist typo3/cms-core >= 14.0.0, < 14.3.3 14.3.3
Packagist typo3/cms-form < 10.4.57 10.4.57
Packagist typo3/cms-form >= 11.0.0, < 11.5.51 11.5.51
Packagist typo3/cms-form >= 12.0.0, < 12.4.46 12.4.46
Packagist typo3/cms-form >= 13.0.0, < 13.4.31 13.4.31
Packagist typo3/cms-form >= 14.0.0, < 14.3.3 14.3.3

Details

As written in the advisory (Markdown source, shown as plain text).

### Problem Backend users with access to the Form Framework were able to use files not ending in `.form.yaml` as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts. ### Solution Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described. ### Credits TYPO3 CMS thanks “Ethan” for reporting this issue, and TYPO3 core & security team member Oliver Hader for fixing it. ### Resources * [TYPO3-CORE-SA-2026-019](https://typo3.org/security/advisory/typo3-core-sa-2026-019)

References

External links from the advisory. They lead to third-party sites.