
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 5.0.0, < 5.3.50
Patched in 5.3.50
Vulnerable: >= 5.4.0-RC1, < 5.7.12
Patched in 5.7.12
Details
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.
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).
This security vulnerability was found by @HDWSec
More composer advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.