CVE-2026-107842

Contao: Protected page content is disclosed to anonymous visitors after contao.search.index_protected is disabled

ModuleSearch decides whether to filter protected pages out of search results based on the current value of contao.search.index_protected, but the authorisation data lives per row in tl_search. Turning the setting off removes
the filter without removing the rows, so protected pages that were indexed while it was on are returned to unauthenticated visitors such as title, URL and context snippet, even though the pages themselves still answer 401.

Credits

This security vulnerability was found by @iRevivalx .

Disclosure of member-only page titles, URLs and indexed text to unauthenticated visitors through the site search. The pages themselves remain access-controlled, so this is not a page-access bypass.

CVE-2026-107842 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.3.50, 5.7.12); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-107842? CVE-2026-107842 is a medium-severity security vulnerability in contao/core-bundle (composer), affecting versions >= 4.0.0, < 5.3.50. It is fixed in 5.3.50, 5.7.12.
2. How severe is CVE-2026-107842? CVE-2026-107842 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of contao/core-bundle are affected by CVE-2026-107842? contao/core-bundle (composer) versions >= 4.0.0, < 5.3.50 is affected.
4. Is there a fix for CVE-2026-107842? Yes. CVE-2026-107842 is fixed in 5.3.50, 5.7.12. Upgrade to this version or later.
5. Is CVE-2026-107842 exploitable, and should I be worried? Whether CVE-2026-107842 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-107842 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-107842?
   • Upgrade contao/core-bundle to 5.3.50 or later
   • Upgrade contao/core-bundle to 5.7.12 or later

Other vulnerabilities in contao/core-bundle