CVE-2026-107851: Contao Improper Access Control Vulnerability

MODERATE
Advisory Identifier: GHSA-5974-gfqc-wrcm
CVSS 4.3
CWE-524 CWE-863
Published
Advisory Summary

CVE-2026-107851 is a MODERATE (CVSS 4.3) improper access control vulnerability (CWE-524: Use of Cache Containing Sensitive Information) affecting Contao libraries in the Packagist ecosystem. The issue involves improper access control in the table access voter. Remediation is available by upgrading affected packages to version 5.7.12.

CVE-2026-107851 at a Glance

CVE Identifier CVE-2026-107851
GHSA Identifier GHSA-5974-gfqc-wrcm
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-524: Use of Cache Containing Sensitive Information
Affected Product Contao
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-107851

To remediate this vulnerability, upgrade all affected Contao dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

contao/core-bundle fixed: 5.7.12
Upgrade contao/core-bundle to 5.7.12
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for contao/core-bundle

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-107851, inspect your project dependencies for Contao:

inspect dependencies for contao/core-bundle

Analyze the terminal output to locate any version of Contao in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.7.12), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-524: Use of Cache Containing Sensitive Information, where the code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. In Contao, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses. ### Vulnerability Details In plain terms: Contao's backend is organized into modules (e.g. "News", "Members"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: "does this user's group actually include this table?" To avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering "is this user allowed to access table X", it only remembers "is this user allowed to access something", without recording which table the answer was actually about. So if a request first checks a table the user IS allowed to see, and then checks a second, completely different table the user is NOT allowed to see, Contao reuses the first answer for the second table too. The user ends up with access to a table their group was never given permission for. ### Technical detail Contao's backend enforces per-table access control through a chain of Symfony security voters. The relevant one is `TableAccessVoter::hasAccessToModule()`, in `core-bundle/src/Security/Voter/DataContainer/TableAccessVoter.php`: ```php private array $canAccessTable = []; private array $canReadAccessTable = []; private function hasAccessToModule(TokenInterface $token, ...): bool { $tokenHash = hash('xxh128', serialize($token)); if (isset($this->canAccessTable[$tokenHash]) || (...)) { return $this->canAccessTable[$tokenHash] ?? $this->canReadAccessTable[$tokenHash]; } $table = $subject->getDataSource(); foreach ($GLOBALS['BE_MOD'] as $modules) { ... return $this->canAccessTable[$tokenHash] = true; // or false } } ``` The cache key, `$tokenHash`, is built only from the current user's security token. It does not include the table being checked. Because `TableAccessVoter` is a normal, shared Symfony service, this cache stays alive for the whole duration of one HTTP request. So the first table checked for a user in a request decides the cached answer for every other table checked afterwards in that same request, whether or not that answer is actually correct for the second table. This is made worse by `DefaultDataContainerVoter`, a low-priority, permissive fallback voter that grants access to any table-related permission unless another voter explicitly denies it. When `TableAccessVoter` gives a wrong "no opinion" answer because of the stale cache, this fallback voter turns that into a full grant. Most database tables in Contao have no second, table-specific check to catch this. Only `tl_content`, `tl_favorites`, `tl_form`, `tl_form_field`, `tl_module`, `tl_image_size(_item)`, `tl_job`, `tl_layout`, `tl_page`, `tl_preview_link`, `tl_undo`, and `tl_user` have one. Tables such as `tl_member` (website member data), `tl_newsletter_recipients` (subscriber e-mail addresses), `tl_news`, `tl_calendar_events`, `tl_faq`, and `tl_comments` rely only on the defective check described above. ### Credits This security vulnerability was found by Sven Jäger of SySS GmbH.

CVE-2026-107851 Affected Contao Versions

1 component(s)
Fixed Versions:
5.7.12
Product / Package Ecosystem Affected Versions Fixed Version
contao/core-bundle
Packagist
≥ 5.7.0
< 5.7.12
5.7.12

References

Frequently Asked Questions

What is CVE-2026-107851?
CVE-2026-107851 is a security vulnerability in Contao involving Improper access control in the table access voter under CWE-524: Use of Cache Containing Sensitive Information.
Which Contao versions are affected?
Affected versions include releases prior to 5.7.12 across affected packages: contao/core-bundle.
What version fixes CVE-2026-107851?
Upgrading to 5.7.12 (or the latest patched release for your respective branch) resolves the vulnerability.
Is contao/core-bundle affected?
Yes, contao/core-bundle is affected in releases prior to 5.7.12. Upgrade your dependency to 5.7.12 or later.
What is the CVSS score of CVE-2026-107851?
CVE-2026-107851 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-107851?
CVE-2026-107851 is classified under CWE-524: Use of Cache Containing Sensitive Information (The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.).
How can I check Packagist dependencies for CVE-2026-107851?
Run the dependency tree command: 'inspect dependencies for contao/core-bundle'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5974-gfqc-wrcm",
  "modified" : "2026-10-09T20:53:42Z",
  "published" : "2026-10-09T20:53:42Z",
  "aliases" : [ "CVE-2026-107851" ],
  "summary" : "Contao: Improper access control in the table access voter",
  "details" : "Due to a caching defect in the security voter that governs table-level access to Contao's Data Container (DCA) backend, a low-privileged, non-admin backend user can obtain unauthorized read, create, update, and delete access to database tables outside their assigned module permissions. This includes tables containing sensitive personal data, such as frontend member records and newsletter subscriber e-mail addresses.\n\n### Vulnerability Details\n\nIn plain terms: Contao's backend is organized into modules (e.g. \"News\", \"Members\"). Every backend user is assigned to a group, and that group decides which modules, and therefore which database tables, they are allowed to work with. Before Contao lets a user touch a table, it is supposed to check: \"does this user's group actually include this table?\"\n\nTo avoid doing that check over and over, Contao remembers the answer for the rest of the request. The problem is that it remembers the answer under the wrong label. Instead of remembering \"is this user allowed to access table X\", it only remembers \"is this user allowed to access something\", without recording which table the answer was actually about.\n \nSo if a request first checks a table the user IS allowed to see, and then checks a second, completely different table the user is NOT allowed to see, Contao reuses the first answer for the second table too. The user ends up with access to a table their group was never given permission for.\n \n### Technical detail\n \nContao's backend enforces per-table access control through a chain of Symfony security voters. The relevant one is\n`TableAccessVoter::hasAccessToModule()`, in `core-bundle/src/Security/Voter/DataContainer/TableAccessVoter.php`:\n \n```php\n    private array $canAccessTable = [];\n    private array $canReadAccessTable = [];\n \n    private function hasAccessToModule(TokenInterface $token, ...): bool\n    {\n        $tokenHash = hash('xxh128', serialize($token));\n \n        if (isset($this->canAccessTable[$tokenHash]) || (...)) {\n            return $this->canAccessTable[$tokenHash] ?? $this->canReadAccessTable[$tokenHash];\n        }\n \n        $table = $subject->getDataSource();\n \n        foreach ($GLOBALS['BE_MOD'] as $modules) {\n            ...\n            return $this->canAccessTable[$tokenHash] = true;  // or false\n        }\n    }\n ```\n\nThe cache key, `$tokenHash`, is built only from the current user's security token. It does not include the table being checked. Because `TableAccessVoter` is a normal, shared Symfony service, this cache stays alive for the whole duration of one HTTP request. So the first table checked for a user in a request decides the cached answer for every other table checked afterwards in that same request, whether or not that answer is actually correct for the second table.\n \nThis is made worse by `DefaultDataContainerVoter`, a low-priority, permissive fallback voter that grants access to any table-related permission unless another voter explicitly denies it. When `TableAccessVoter` gives a wrong \"no opinion\" answer because of the stale cache, this fallback voter turns that into a full grant.\n \nMost database tables in Contao have no second, table-specific check to catch this. Only `tl_content`, `tl_favorites`, `tl_form`, `tl_form_field`, `tl_module`, `tl_image_size(_item)`, `tl_job`, `tl_layout`, `tl_page`, `tl_preview_link`, `tl_undo`, and `tl_user` have one. Tables such as `tl_member` (website member data), `tl_newsletter_recipients` (subscriber e-mail addresses), `tl_news`, `tl_calendar_events`, `tl_faq`, and `tl_comments` rely only on the defective check described above.\n\n### Credits\n\nThis security vulnerability was found by Sven Jäger of SySS GmbH.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "contao/core-bundle"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.7.0"
      }, {
        "fixed" : "5.7.12"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/contao/contao/security/advisories/GHSA-5974-gfqc-wrcm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/contao/contao/commit/9d6f582a4cc6a758ce11d1043fc9c0ba62c5f4c9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/contao/contao"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/contao/contao/releases/tag/5.7.12"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-524", "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-09T20:53:42Z",
    "nvd_published_at" : null
  }
}