NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2026-104881 — newsletter-bundle

MEDIUMFix: contao/contao#10153

CVE-2026-104881 is a medium-severity (CVSS 4.3) vulnerability in contao/newsletter-bundle. A fix is available for contao/newsletter-bundle — see the affected versions and patch details below.

contao/newsletter-bundle: Contao newsletter custom actions bypass channel-scoped authorization

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 21, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐘contao/newsletter-bundle🐘contao/newsletter-bundle

Real-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

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

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcontao/newsletter-bundle≥ 5.0.0&&< 5.3.505.3.50composer require contao/newsletter-bundle:^5.3.50
🐘Packagistcontao/newsletter-bundle≥ 5.4.0-RC1&&< 5.7.125.7.12composer require contao/newsletter-bundle:^5.7.12

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/newsletter-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update contao/newsletter-bundle to 5.3.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-104881 is resolved across your whole dependency graph.

  3. 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

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` /
O3 Security · Impact-Aware SCA

Is CVE-2026-104881 in your dependencies?

Find it across Packagist, including transitive dependencies.