How severe is GHSA-9jh5-qf84-x6pr?

GHSA-9jh5-qf84-x6pr has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9jh5-qf84-x6pr?

GHSA-9jh5-qf84-x6pr affects the following packages: contao/core-bundle (Packagist), contao/core-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-9jh5-qf84-x6pr?

Update contao/core-bundle to 4.13.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jh5-qf84-x6pr is resolved across your whole dependency graph.

How do I detect GHSA-9jh5-qf84-x6pr in my Packagist dependencies?

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.

How do I mitigate GHSA-9jh5-qf84-x6pr if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-9jh5-qf84-x6pr actively exploited in the wild?

No public exploit code has been indexed for GHSA-9jh5-qf84-x6pr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9jh5-qf84-x6pr?

GHSA-9jh5-qf84-x6pr has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9jh5-qf84-x6pr?

GHSA-9jh5-qf84-x6pr is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9jh5-qf84-x6pr published, and has it been updated?

GHSA-9jh5-qf84-x6pr was published on April 9, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

Contao: Possible cookie sharing with external domains while checking protected pages for broken linksGHSA-9jh5-qf84-x6pr

HIGHFix: contao/contao@73a2770

GHSA-9jh5-qf84-x6pr is a high-severity (CVSS 8.3) Information Exposure vulnerability in contao/core-bundle. A fix is available for contao/core-bundle — see the affected versions and patch details below.

Also known asCVE-2024-28235

Published

Apr 9, 2024

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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-9jh5-qf84-x6pr.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘contao/core-bundle🐘contao/core-bundle

Real-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 the crawler is set to crawl protected pages, it sends the cookie header to externals URLs.

Patches

Update to Contao 4.13.40 or 5.3.4.

Workarounds

Disable crawling protected pages.

References

https://contao.org/en/security-advisories/session-cookie-disclosure-in-the-crawler

For more information

If you have any questions or comments about this advisory, open an issue in contao/contao.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/core-bundle`	≥ 4.9.0&&< 4.13.40	4.13.40`composer require contao/core-bundle:^4.13.40`
🐘Packagist	`contao/core-bundle`	≥ 5.0.0-RC1&&< 5.3.4	5.3.4`composer require contao/core-bundle:^5.3.4`

Affected Products

1 product · 2 configurations

Application

contaocontao

≥ 5.0.0 && < 5.3.4

range

Detection & mitigation playbook

Open-source dependency

Detect
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 4.13.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jh5-qf84-x6pr is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact If the crawler is set to crawl protected pages, it sends the cookie header to externals URLs. ### Patches Update to Contao 4.13.40 or 5.3.4. ### Workarounds Disable crawling protected pages. ### References https://contao.org/en/security-advisories/session-cookie-disclosure-in-the-crawler ### For more information If you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).