Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-107848 Overview
CVE-2026-107848 is a Cross-Site Request Forgery (CSRF) vulnerability [CWE-352] in Contao, an open source content management system. The RequestTokenListener validates the REQUEST_TOKEN only for POST requests, while the declarative GET guard runs only when an act parameter is present. Backend actions dispatched through the key parameter can therefore execute without a CSRF token when an authenticated backend user loads an attacker-controlled URL. Reachable actions remain limited to modules available to the targeted user. The flaw affects Contao versions 4.0.0 through 5.3.49 and 5.7.11, and is fixed in versions 5.3.50 and 5.7.12.
Critical Impact
Authenticated backend users who visit an attacker-controlled URL can trigger destructive or state-changing backend actions without a valid CSRF token.
Affected Products
- Contao versions 4.0.0 through 5.3.49
- Contao versions 5.4.0 through 5.7.11
- Any backend module exposing actions via the key parameter
Discovery Timeline
- 2026-10-09 - CVE CVE-2026-107848 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-107848
Vulnerability Analysis
Contao's backend protects state-changing requests with a request token (CSRF token). The RequestTokenListener enforces this check for all POST requests. For GET requests, protection is delegated to a declarative guard that inspects the act query parameter. Backend routes dispatched through the key parameter bypass both checks because they travel as GET requests without an act value.
An authenticated backend user who loads an attacker-controlled page can issue a cross-origin GET request to the Contao backend. The browser attaches the user's session cookie, and the targeted action executes under the user's privileges. The advisory limits impact to actions available to the victim's modules and documents destructive or state-changing behavior rather than privilege escalation.
Root Cause
The root cause is inconsistent CSRF enforcement across HTTP methods and dispatch parameters. The listener couples token validation to request method and the presence of the act parameter, leaving key-parameter actions unguarded on GET requests.
Attack Vector
Exploitation requires an authenticated Contao backend user to visit an attacker-controlled URL or page that references the vulnerable backend endpoint. User interaction is required, and the attacker needs prior knowledge of the target's reachable backend modules.
// Patch excerpt: core-bundle/contao/dca/tl_opt_in.php
use Contao\Backend;
use Contao\Controller;
use Contao\CoreBundle\DataContainer\DataContainerOperation;
+use Contao\CoreBundle\Exception\InvalidRequestTokenException;
use Contao\Database;
use Contao\DataContainer;
use Contao\DC_Table;
+use Contao\Input;
use Contao\Message;
use Contao\OptInModel;
use Contao\System;
+use Symfony\Component\Security\Csrf\CsrfToken;
Source: Contao commit 34dd27e
The patch introduces explicit CSRF token validation on key-parameter actions by importing InvalidRequestTokenException, CsrfToken, and Input, then validating the submitted token before executing the action. A parallel change appears in manager-bundle/src/Controller/DebugController.php, which now also imports ContaoCsrfTokenManager and enforces token validation.
Detection Methods for CVE-2026-107848
Indicators of Compromise
- Backend GET requests containing a key parameter without a corresponding REQUEST_TOKEN value in logs
- Cross-origin Referer headers on backend requests originating from unknown or external domains
- Unexpected state changes in backend data (deletions, status updates) correlated with recent authenticated backend sessions
Detection Strategies
- Review web server access logs for backend URLs containing key= without rt= or an equivalent token parameter
- Correlate backend action audit entries with user browsing activity to spot externally referred requests
- Alert on backend sessions that execute state-changing actions immediately after navigating from an external referrer
Monitoring Recommendations
- Enable verbose logging on the Contao backend controller to capture key and act parameter usage per authenticated session
- Monitor the tl_log table for destructive actions issued outside normal administrator workflows
- Track outbound links from internal communications (email, chat) that resolve to backend URLs with key parameters
How to Mitigate CVE-2026-107848
Immediate Actions Required
- Upgrade Contao to version 5.3.50 or 5.7.12 as applicable to the deployed branch
- Terminate active backend sessions and require re-authentication after patching
- Audit recent backend logs for suspicious key-parameter requests originating from external referrers
Patch Information
The fix is included in Contao 5.3.50 and 5.7.12. The upstream commit 34dd27e adds explicit CSRF token validation to backend actions dispatched through the key parameter. Release notes are published in the Contao 5.7.12 release, and advisory details are available in GHSA-9ff2-p842-45wq.
Workarounds
- Restrict backend access to a VPN or IP allowlist to reduce exposure to cross-origin requests
- Instruct backend users to log out when not actively administering the site and to avoid clicking untrusted links while authenticated
- Deploy a web application firewall rule that rejects backend GET requests containing a key parameter without a valid rt token
# Example: upgrade Contao via Composer to a patched release
composer require contao/manager-bundle:^5.7.12 --with-all-dependencies
# or for the 5.3 LTS branch
composer require contao/manager-bundle:^5.3.50 --with-all-dependencies
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

