Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-104882: Authorization bypass in Contao core-bundle CSV import wizard

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-104882CWE-639

CVE-2026-104882 is an authorization bypass in the contao/core-bundle CSV import wizard. Custom backend module key actions are dispatched after a module-level access check without per-record authorization. An authenticated non-admin editor can therefore target records outside their authorized page or form scope and overwrite tableitems, listitems, or options in tl_content or tl_form_field records. The vulnerability enables blind content overwrite; imported values are serialized arrays of plain strings, not objects, and do not constitute object injection.

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.

Successful exploitation allows unauthorized modification of content or form-field records beyond an editor's assigned scope. The vulnerability has a CVSS v3.0 base score of 6.5, with high integrity impact and no assessed confidentiality or availability impact. It does not provide object injection.

Remediation

Patch, then assume compromise.

Upgrade contao/core-bundle and related packages to the applicable fixed release for the installed branch: 5.3.50 or 5.7.12.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-104882The repository contains 28 files: 11 code/build files, 12 captured evidence files, and five documentation/metadata files. Python clients in exploit/exploit.py and poc/poc.py drive a custom HTTP wrapper; a PHP harness loads one of two vendored BackendCsvImportController implementations. Dockerfiles, run-lab.sh, and Makefile build and compare vulnerable and patched containers on an isolated Podman network. No established exploitation framework is used. The supplied vulnerable controller imports CSV data and updates a record selected by DataContainer table/id without a per-record authorization check. Its list, table, and option import actions share this write path. The fixed implementation retrieves the current record and calls denyAccessUnlessGranted with a DataContainer UpdateAction before updating. This supports the demonstrated authorization-bypass mechanism. The repository attributes it to CVE-2026-104882, affecting contao/core-bundle before 5.3.50 and fixed by commit eb8088bcd; those external identifiers and source provenance were not independently verified. The actual demonstration is narrower than the README's 'standalone full-chain exploit' wording: clients only POST a scope selector to the lab's /import endpoint. The harness creates the CSV locally, fixes the target to tl_content id=1, and uses an in-memory Doctrine update recorder. No real login, backend key-action dispatch, multipart upload, record selection, or persistent database modification is implemented. Thus the supplied evidence demonstrates a controller-level differential, not successful exploitation of a deployed Contao instance. Broader impact on listitems and tl_form_field.options follows the shared controller path but is not directly exercised by this harness. The basic hardcoded payload overwrites CSV-backed content; it does not execute commands, establish a shell, exfiltrate data, or perform PHP object injection. Captured outputs report an unauthorized update for the vulnerable version and denial for the fixed version. Several client branches can mislabel unexpected or empty responses as safe, especially the standalone client and exploit/probe modes; check mode handles indeterminate results more carefully. The Dockerfile's rm -rf removes package-manager cache during image construction and is not evidence of a fake exploit. The analyzed git reference and archive size were not supplied; unknown and 0 are placeholders.googlesky · Disclosed Nov 21, 2026 · python · php · webOperational
FAQ

Frequently asked questions

Is CVE-2026-104882 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-104882 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-104882?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-104882, the earliest disclosed Nov 21, 2026.
Is there a patch for CVE-2026-104882?
Upgrade contao/core-bundle and related packages to the applicable fixed release for the installed branch: 5.3.50 or 5.7.12.
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.