CVE-2026-104883 is a high-severity (CVSS 7.2) remote code execution vulnerability in contao/core-bundle. A fix is available for contao/core-bundle — see the affected versions and patch details below.
contao/core-bundle: Non-admin users can self-grant permissions that implicitly make them administrators
Real-World Exposure
contao/core-bundle🐘contao/core-bundleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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):
- As admin, create a non-admin backend group with the
user(orgroup) module (a delegated user manager), and a user in it. Confirm the user cannot accesstpl_editor(blocked by the 5.7.3 voter). - As that non-admin, edit a group/account: add
themesto the modules field andtheme_importto the themes field (both accepted - onlytpl_editoris 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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | contao/core-bundle | ≥ 5.0.0&&< 5.3.50 | 5.3.50composer require contao/core-bundle:^5.3.50 |
| 🐘Packagist | contao/core-bundle | ≥ 5.4.0-RC1&&< 5.7.12 | 5.7.12composer require contao/core-bundle:^5.7.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/core-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update contao/core-bundle to 5.3.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-104883 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-104883 in your dependencies?
Find it across Packagist, including transitive dependencies.