CVE-2026-104881 json
contao/newsletter-bundle: Contao newsletter custom actions bypass channel-scoped authorization
published 1h ago modified 1h ago also GHSA-3r9g-pfhv-3228
- cvss
- 4.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Channel access is enforced only by the DataContainer voters (`NewsletterChannelAccessVoter` / `NewsletterRecipientsAccessVoter`, requiring USER_CAN_EDIT_CHANNEL), whose `supportsType()` fires exclusively for Create/Read/Update/DeleteAction subjects dispatched inside DC_Table's create/edit/delete methods. The newsletter custom key-actions are dispatched directly by `Backend::getBackendModule()` (Backend.php:324-327) after only the module-level `USER_CAN_ACCESS_MODULE` check; the DC_Table constructor runs no per-record ReadAction vote for a key-action. `Newsletter.php` contains no `isGranted` / `denyAccess` / `isAdmin` / `hasAccess` calls, and none of the newsletter DCAs have a `checkPermission` onload callback.
## Impact
A channel-scoped newsletter editor can inject recipients into, mass-mail, and in some versions, delete/denylist recipients of channels they are not authorized to edit - defeating the per-channel permission model (integrity + abuse of the mail-sending capability).
## Credits
This security vulnerability was found by @HDWSec
Patch / fix
- packagist contao/newsletter-bundle 5.3.50, 5.7.12
- github.com/contao/contao@1471dca commit
- github.com/contao/contao@17fe7a5 commit
- github.com/contao/contao@a58eb71 commit
- github.com/contao/contao#10153 pull request
Is CVE-2026-104881 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | contao/newsletter-bundle | >=5.0.0, <5.3.50 >=5.4.0-RC1, <5.7.12 |
5.3.50 5.7.12 |
Classification
References
-
github.com
/contao/contao/pull/10153
web
-
github.com
/contao/contao/commit/1471dcaf4fe3d07a415e756dc54ce1f46d2ee879
web
-
github.com
/contao/contao/commit/17fe7a52fc5df47209603708c6136a060f8eea43
web
-
github.com
/contao/contao/commit/a58eb71ef5a7a87da9d90980579dbeb6688448b4
web
-
github.com
/contao/contao/security/advisories/GHSA-3r9g-pfhv-3228
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/contao/contao/CVE-2026-104881.yaml
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/contao/newsletter-bundle/CVE-2026-104881.yaml
web
-
github.com
/contao/contao
package
-
github.com
/contao/contao/blob/a11109b60dedcbd99e32a4e8550afdadb500f2c5/CHANGELOG.md
web
-
github.com
/contao/contao/blob/a6543f49a92187a7368f51b290179c4795386e23/CHANGELOG.md
web
-
github.com
/contao/contao/tree/5.3.50
web
-
github.com
/contao/contao/tree/5.7.12
web
Sources
- GitHub Advisory GHSA-3r9g-pfhv-3228
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.