Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-104881: Channel-scoped authorization bypass in Contao Newsletter Bundle

Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-104881CWE-862

CVE-2026-104881 is an authorization bypass in contao/newsletter-bundle. Newsletter custom actions perform only a module-level access check instead of the per-record authorization enforced for standard create, read, update, and delete actions. Consequently, authenticated newsletter editors with channel-scoped permissions can perform certain actions against channels outside their authorized scope. The vulnerability has a CVSS v3.0 base score of 4.3.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An authenticated, channel-scoped newsletter editor can inject recipients into unauthorized channels and send mass mail through those channels. In some affected versions, the editor can also delete or denylist recipients in unauthorized channels. This compromises recipient integrity and enables unauthorized use of mail-sending capabilities. The assessed CVSS impact is low integrity impact, with no confidentiality or availability impact.

Remediation

Patch, then assume compromise.

Upgrade contao/newsletter-bundle to the applicable fixed release: version 5.3.50 for the affected release range beginning at 5.0.0, or version 5.7.12 for the affected release range beginning at 5.4.0-RC1. Update related packages as required by dependency constraints.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-104881This standalone repository is a containerized differential authorization-bypass PoC, not a framework module. It attributes the issue to CVE-2026-104881 and claims contao/newsletter-bundle versions before 5.3.50 are affected. The described root cause is that newsletter key-actions bypass per-record channel voters that normally run for DataContainer CRUD operations. The visible fixed send method adds denyAccessUnlessGranted with a ReadAction before database access. The 30 files include four Python files, five PHP files, one Bash script, three build definitions, documentation/metadata, and 12 captured evidence files. The code-file count includes the Dockerfiles and Makefile. exploit/exploit.py is a minimal HTTP client; poc/poc.py adds readiness polling, check/exploit/probe/mitigation modes, and in-scope controls. lab/service.py exposes POST /send and GET /info, lab/harness.php invokes the selected method, lab/stubs.php mocks dependencies, and lab/gen.py assembles the Newsletter class from the vendored fragments. run-lab.sh builds and compares vulnerable/fixed containers using Podman. The demonstrated capability is narrower than the README's 'full-chain exploit' description. Neither client interacts with native Contao routes or authenticates a real backend user. The wrapper accepts a client-provided scope, the security stub translates it into a grant decision, and the database stub always returns zero rows. Consequently, the vulnerable method returns early and the fixed method denies access; no newsletter delivery, recipient import, or production authorization chain is exercised. importRecipients is discussed but its implementation and execution are absent. Some client modes also classify unexpected responses as safe/protected, so negative output is not reliable production assurance. Captured evidence is consistent with the laboratory differential, but execution, CVE validity, upstream provenance, and the claimed absence of remaining bypasses were not independently verified. Both vendored send listings are partially truncated in the supplied content. No reverse shell, persistence, exfiltration destination, or malicious operator-side payload is evident; the Dockerfile's rm -rf is ordinary package-cache cleanup. The repository URL is inferred from CITATION.cff. The analyzed Git ref and archive size were not provided; the empty ref and zero size represent unknown metadata.googlesky · Disclosed Nov 21, 2026 · python · php · webPoC
FAQ

Frequently asked questions

Is CVE-2026-104881 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-104881 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-104881?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-104881, the earliest disclosed Nov 21, 2026.
Is there a patch for CVE-2026-104881?
Upgrade contao/newsletter-bundle to the applicable fixed release: version 5.3.50 for the affected release range beginning at 5.0.0, or version 5.7.12 for the affected release range beginning at 5.4.0-RC1. Update related packages as required by dependency constraints.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.