HighGHSA-pjpj-v387-x4vqCVE-2026-11607

TYPO3 CMS has Broken Access Control in its Form Framework

Published 12 Jun 2026 · Updated 10 Sept 2026

Affected packages

Affected
<10.4.57
Fixed in
10.4.57
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.57
Affected
>=11.0.0 <11.5.51
Fixed in
11.5.51
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.51
Affected
>=12.0.0 <12.4.46
Fixed in
12.4.46
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^12.4.46
Affected
>=13.0.0 <13.4.31
Fixed in
13.4.31
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^13.4.31
Affected
>=14.0.0 <14.3.3
Fixed in
14.3.3
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^14.3.3
Affected
<10.4.57
Fixed in
10.4.57
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^10.4.57
Affected
>=11.0.0 <11.5.51
Fixed in
11.5.51
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^11.5.51
Affected
>=12.0.0 <12.4.46
Fixed in
12.4.46
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^12.4.46
Affected
>=13.0.0 <13.4.31
Fixed in
13.4.31
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^13.4.31
Affected
>=14.0.0 <14.3.3
Fixed in
14.3.3
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^14.3.3

Details

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

Is GHSA-pjpj-v387-x4vq 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

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.