Advisory record · GHSA-x2rp-9qf7-2fmq

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

CVSS 5.3 MediumEPSS 0.0026 · 18th percentile

Published by the GitHub Advisory Database at 9 Oct 2026, 20:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
contao/core-bundlePackagist>=4.0.0, <5.3.50 || >=5.4.0-RC1, <5.7.125.3.50, 5.7.12
Identifiers
GHSA-x2rp-9qf7-2fmq · CVE-2026-107842 · PKSA-bmqh-y7sv-p1st
Weakness (CWE)
CWE-200
Published
9 Oct 2026
Updated
9 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Contao's contao/core-bundle is affected in versions from 4.0.0 before 5.3.50 and from 5.4.0-RC1 before 5.7.12. If the contao.search.index_protected setting is turned off after protected pages were indexed, the site search can return titles, URLs and text snippets of those member-only pages to anonymous visitors, because the stored search rows are not removed. An unauthenticated visitor can see this through ordinary site search, though the pages themselves still require authentication. Upgrade to 5.3.50 or 5.7.12, which are the fixed versions.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 18th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 25 Aug 2026, 06:40 UTC Confirmed by Packagist
  2. 31 Oct 2026, 13:53 UTC First seen by agentprime
  3. 31 Oct 2026, 13:53 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.