GHSA-w53m-gxvg-vx7p is a medium-severity (CVSS 5.3) Information Exposure vulnerability in contao/core-bundle. A fix is available for contao/core-bundle — see the affected versions and patch details below.
Contao can disclose sensitive information in the news module
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-w53m-gxvg-vx7p.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-w53m-gxvg-vx7p plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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
If a news feed contains protected news archives, their news items are not filtered and become publicly available in the RSS feed.
Patches
Update to Contao 5.3.38 or 5.6.1.
Workarounds
Do not add protected news archives to the news feed page.
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 | ≥ 5.0.0-RC1&&< 5.3.38 | 5.3.38composer require contao/core-bundle:^5.3.38 |
| 🐘Packagist | contao/core-bundle | ≥ 5.4.0-RC1&&< 5.6.1 | 5.6.1composer require contao/core-bundle:^5.6.1 |
| 🐘Packagist | contao/contao | ≥ 5.0.0-RC1&&< 5.3.38 | 5.3.38composer require contao/contao:^5.3.38 |
| 🐘Packagist | contao/contao | ≥ 5.4.0-RC1&&< 5.6.1 | 5.6.1composer require contao/contao:^5.6.1 |
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update contao/core-bundle to 5.3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w53m-gxvg-vx7p 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w53m-gxvg-vx7p can be triaged on real exposure rather than presence alone.
Tailored to GHSA-w53m-gxvg-vx7p. 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-w53m-gxvg-vx7p in your dependencies?
O3 Security finds GHSA-w53m-gxvg-vx7p across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.