contao/core-bundle: Non-admin users can self-grant permissions that implicitly make them administrators
Published 20 Nov 2026 · Updated 21 Nov 2026
Is your project on an affected contao/core-bundle?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=5.0.0 <5.3.50
- Fixed in
- 5.3.50
composer require contao/core-bundle:^5.3.50- Affected
- >=5.4.0-RC1 <5.7.12
- Fixed in
- 5.7.12
composer require contao/core-bundle:^5.7.12Details
Commit 2b83a60f7763 (5.7.3) hardened the template editor: it added TemplateEditorModuleVoter + CheckTemplateEditorSaveListener so a non-admin cannot self-grant the tpl_editor backend module (editable PHP-capable templates permit server-side code execution). That voter supports only the modules field and the literal value tpl_editor.
The equally RCE-capable theme_import capability lives in a different field - the themes checkbox field (tl_user_group.php:98-105 options include theme_import; identical on tl_user.php:248-253) - which has no save_callback and no voter. TemplateEditorModuleVoter is the only DC voter registered for tl_user_group, and it does not cover the themes field. So a delegated user manager can add theme_import to their own (or a managed) account.
Live repro (Contao 5.7.9):
1. As admin, create a non-admin backend group with the user (or group) module (a delegated user manager), and a user in it. Confirm the user cannot access tpl_editor (blocked by the 5.7.3 voter).
2. As that non-admin, edit a group/account: add themes to the modules field and theme_import to the themes field (both accepted - only tpl_editor is blocked). Re-authenticate.
Impact
A delegated user/group manager (a role explicitly not trusted with template/code access) escalates to arbitrary PHP execution on the server, fully compromising the installation. This bypasses the exact protection the 5.7.3 tpl_editor fix introduced.
Credits
This security vulnerability was found by @HDWSec
Is GHSA-r9qp-pqx5-8369 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 contao/core-bundle, and gives you the command that fixes it.
More advisories for contao/core-bundle
- MediumCVE-2026-104884contao/core-bundle: Cross-site scripting in the frontend search results · 20 Nov 2026
- MediumCVE-2026-104882contao/core-bundle: Improper access control in the CSV import wizard · 20 Nov 2026
- MediumCVE-2026-107842Contao: Protected page content is disclosed to anonymous visitors after contao.search.index_protected is disabled · 9 Oct 2026
- MediumCVE-2026-107843Contao: The registration module re-sends activation mails · 9 Oct 2026
- LowCVE-2026-107848Contao: Cross-site request forgery in custom backend actions · 9 Oct 2026
- MediumCVE-2026-107844Contao: Path traversal in the images controller · 9 Oct 2026
References
- Linkgithub.com/contao/contao/security/advisories/GHSA-r9qp-pqx5-8369
- Linkgithub.com/contao/contao/pull/10153
- Linkgithub.com/contao/contao/commit/211498f28d4c86484b96eb0612c1193105b79e51
- Linkgithub.com/contao/contao/commit/a58eb71ef5a7a87da9d90980579dbeb6688448b4
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/contao/contao/CVE-2026-104883.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/contao/core-bundle/CVE-2026-104883.yaml
- Packagegithub.com/contao/contao
- Linkgithub.com/contao/contao/blob/a11109b60dedcbd99e32a4e8550afdadb500f2c5/CHANGELOG.md
- Linkgithub.com/contao/contao/blob/a6543f49a92187a7368f51b290179c4795386e23/CHANGELOG.md
- Linkgithub.com/contao/contao/tree/5.3.50
- Linkgithub.com/contao/contao/tree/5.7.12
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.