Skip to content

Contao applies improper access control in the back end voters

Moderate severity GitHub Reviewed Published Aug 28, 2025 in contao/contao • Updated Aug 28, 2025

Package

composer contao/contao (Composer)

Affected versions

>= 5.0.0, < 5.3.38
>= 5.4.0-RC1, < 5.6.1

Patched versions

5.3.38
5.6.1
composer contao/core-bundle (Composer)
>= 5.0.0, < 5.3.38
>= 5.4.0-RC1, < 5.6.1
5.3.38
5.6.1

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.

References

@leofeyer leofeyer published to contao/contao Aug 28, 2025
Published to the GitHub Advisory Database Aug 28, 2025
Reviewed Aug 28, 2025
Published by the National Vulnerability Database Aug 28, 2025
Last updated Aug 28, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(7th percentile)

Weaknesses

Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Learn more on MITRE.

CVE ID

CVE-2025-57758

GHSA ID

GHSA-7m47-r75r-cx8v

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.