How severe is GHSA-2xmj-8wmq-7475?

GHSA-2xmj-8wmq-7475 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2xmj-8wmq-7475?

GHSA-2xmj-8wmq-7475 affects the following packages: contao/core-bundle (Packagist), contao/contao (Packagist), contao/core-bundle (Packagist), contao/core-bundle (Packagist), contao/contao (Packagist), contao/contao (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2xmj-8wmq-7475?

Update contao/core-bundle to 4.13.56 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xmj-8wmq-7475 is resolved across your whole dependency graph.

How do I detect GHSA-2xmj-8wmq-7475 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-2xmj-8wmq-7475 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-2xmj-8wmq-7475 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2xmj-8wmq-7475 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-2xmj-8wmq-7475?

GHSA-2xmj-8wmq-7475 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th 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-2xmj-8wmq-7475?

GHSA-2xmj-8wmq-7475 is classified as Information Exposure (CWE-200), CWE-612 (CWE-612). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2xmj-8wmq-7475 published, and has it been updated?

GHSA-2xmj-8wmq-7475 was published on August 28, 2025 and was last updated on August 28, 2025. 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

MEDIUM severity

Contao discloses sensitive information in the front end search indexGHSA-2xmj-8wmq-7475

MEDIUMFix: contao/contao@a03976c

GHSA-2xmj-8wmq-7475 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.

Also known asCVE-2025-57756

Published

Aug 28, 2025

Updated

Aug 28, 2025

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

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

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-2xmj-8wmq-7475.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs22th percentile — riskier than 22% 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

6 pkgs affected

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

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

Protected content elements that are rendered as fragments are indexed and become publicly available in the front end search.

Patches

Update to Contao 4.13.56, 5.3.38 or 5.6.1.

Workarounds

Disable the front end search.

For more information

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

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/core-bundle`	≥ 4.9.14&&< 4.13.56	4.13.56`composer require contao/core-bundle:^4.13.56`
🐘Packagist	`contao/contao`	≥ 4.9.14&&< 4.13.56	4.13.56`composer require contao/contao:^4.13.56`
🐘Packagist	`contao/core-bundle`	≥ 5.0.0-RC1&&< 5.3.38	5.3.38`composer require contao/core-bundle:^5.3.38`
🐘Packagist	`contao/core-bundle`	≥ 5.4.0-RC1&&< 5.6.1	5.6.1`composer require contao/core-bundle:^5.6.1`
🐘Packagist	`contao/contao`	≥ 5.0.0-RC1&&< 5.3.38	5.3.38`composer require contao/contao:^5.3.38`
🐘Packagist	`contao/contao`	≥ 5.4.0-RC1&&< 5.6.1	5.6.1`composer require contao/contao:^5.6.1`

Affected Products

1 product · 4 configurations

Application

contaocontao

≥ 5.4.0 && ≤ 4.9.14

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.56 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xmj-8wmq-7475 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 Protected content elements that are rendered as fragments are indexed and become publicly available in the front end search. ### Patches Update to Contao 4.13.56, 5.3.38 or 5.6.1. ### Workarounds Disable the front end search. ### 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).