Contao CMS up to 5.3.37/5.6.0 privileges management

Summaryinfo

A vulnerability, which was classified as critical, has been found in Contao CMS up to 5.3.37/5.6.0. Affected by this vulnerability is an unknown functionality. This manipulation causes privileges management. This vulnerability is registered as CVE-2025-57759. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Contao CMS up to 5.3.37/5.6.0. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Contao is an Open Source CMS. In versions starting from 5.3.0 and prior to 5.3.38 and 5.6.1, under certain conditions, back end users may be able to edit fields of pages and articles without having the necessary permissions. This issue has been patched in versions 5.3.38 and 5.6.1. There are no workarounds.

The advisory is shared at github.com. This vulnerability is known as CVE-2025-57759 since 08/19/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 5.3.38 or 5.6.1 eliminates this vulnerability. Applying the patch 80ee7db12d55ad979d9b1b180f273d4e2668851f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1920). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Open Source Contao

Productinfo

Type

• Content Management System

Vendor

• Contao

Name

• CMS

Version

• 5.0
• 5.1
• 5.2
• 5.3
• 5.3.0
• 5.3.1
• 5.3.2
• 5.3.3
• 5.3.4
• 5.3.5
• 5.3.6
• 5.3.7
• 5.3.8
• 5.3.9
• 5.3.10
• 5.3.11
• 5.3.12
• 5.3.13
• 5.3.14
• 5.3.15
• 5.3.16
• 5.3.17
• 5.3.18
• 5.3.19
• 5.3.20
• 5.3.21
• 5.3.22
• 5.3.23
• 5.3.24
• 5.3.25
• 5.3.26
• 5.3.27
• 5.3.28
• 5.3.29
• 5.3.30
• 5.3.31
• 5.3.32
• 5.3.33
• 5.3.34
• 5.3.35
• 5.3.36
• 5.3.37
• 5.4
• 5.5
• 5.6.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion