GHSA-4mvc-qc5w-v5qr
MEDIUMGHSA-4mvc-qc5w-v5qr is a medium-severity (CVSS 5.3) Incorrect Default Permissions vulnerability in contao/core-bundle. O3 Security confirms whether GHSA-4mvc-qc5w-v5qr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Information disclosure in the Contao backend
Real-World Exposure
contao/core-bundle🐘contao/core-bundle🐘contao/contao🐘contao/contaoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Back end users can manipulate the details view URL to show pages and articles that have not been enabled for them.
Patches
Update to Contao 4.4.46 or 4.8.6.
Workarounds
None.
References
https://contao.org/en/security-advisories/information-disclosure-in-the-back-end
For more information
If you have any questions or comments about this advisory, open an issue in contao/contao.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | contao/core-bundle | ≥ 4.0.0&&< 4.4.46 | 4.4.46 |
| 🐘Packagist | contao/core-bundle | ≥ 4.5.0&&< 4.8.6 | 4.8.6 |
| 🐘Packagist | contao/contao | ≥ 4.0.0&&< 4.4.46 | 4.4.46 |
| 🐘Packagist | contao/contao | ≥ 4.5.0&&< 4.8.6 | 4.8.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/core-bundle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update contao/core-bundle to 4.4.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4mvc-qc5w-v5qr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4mvc-qc5w-v5qr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-4mvc-qc5w-v5qr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4mvc-qc5w-v5qr in your dependencies?
O3 detects GHSA-4mvc-qc5w-v5qr across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.