How severe is CVE-2025-57758?

CVE-2025-57758 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-57758?

CVE-2025-57758 affects the following packages: contao/core-bundle (Packagist), contao/core-bundle (Packagist), contao/contao (Packagist), contao/contao (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-57758?

Update contao/core-bundle to 5.3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-57758 is resolved across your whole dependency graph.

How do I detect CVE-2025-57758 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 CVE-2025-57758 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-57758 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-57758 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 CVE-2025-57758?

CVE-2025-57758 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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 CVE-2025-57758?

CVE-2025-57758 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-57758 published, and has it been updated?

CVE-2025-57758 was published on August 28, 2025 and was last updated on October 28, 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

MEDIUM severity

CVE-2025-57758 — core-bundle

MEDIUMFix: contao/contao@3f05c60

CVE-2025-57758 is a medium-severity (CVSS 4.3) CWE-284 vulnerability in contao/core-bundle. A fix is available for contao/core-bundle — see the affected versions and patch details below.

Contao has improper access control in the back end voters

Also known asGHSA-7m47-r75r-cx8v

Published

Aug 28, 2025

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 5, 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 CVE-2025-57758.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

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

4 pkgs affected

🐘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

The table access voter in the back end doesn't check if a user is allowed to access the corresponding module.

Patches

Update to Contao 5.3.38 or 5.6.1.

Workarounds

Do not rely solely on the voter and additionally check USER_CAN_ACCESS_MODULE.

For more information

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/core-bundle`	≥ 5.0.0&&< 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&&< 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 · 2 configurations

Application

contaocontao

≥ 5.4.0 && < 5.6.1

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 5.3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-57758 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact The table access voter in the back end doesn't check if a user is allowed to access the corresponding module. ### Patches Update to Contao 5.3.38 or 5.6.1. ### Workarounds Do not rely solely on the voter and additionally check `USER_CAN_ACCESS_MODULE`. ### 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).