Summary
Workarounds
None.
For more information
If you have any questions or comments about this advisory, open an issue in contao/contao.
Impact
Under certain conditions, back end users may be able to edit fields of pages and articles without having the necessary permissions.
The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.
CVE-2025-57759 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.3.38, 5.6.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Update to Contao 5.3.38 or 5.6.1.
Frequently Asked Questions
- What is CVE-2025-57759? CVE-2025-57759 is a medium-severity improper privilege management vulnerability in contao/core-bundle (composer), affecting versions >= 5.3.0, < 5.3.38. It is fixed in 5.3.38, 5.6.1. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- How severe is CVE-2025-57759? CVE-2025-57759 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2025-57759?
contao/core-bundle(composer) (versions >= 5.3.0, < 5.3.38)contao/contao(composer) (versions >= 5.3.0, < 5.3.38)
- Is there a fix for CVE-2025-57759? Yes. CVE-2025-57759 is fixed in 5.3.38, 5.6.1. Upgrade to this version or later.
- Is CVE-2025-57759 exploitable, and should I be worried? Whether CVE-2025-57759 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-57759 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-57759?
- Upgrade
contao/core-bundleto 5.3.38 or later - Upgrade
contao/core-bundleto 5.6.1 or later - Upgrade
contao/contaoto 5.3.38 or later - Upgrade
contao/contaoto 5.6.1 or later
- Upgrade