Skip to content
Fencer Intel
medium 4.3

CVE-2025-57758 json

Contao has improper access control in the back end voters

published last yr. modified 4mo ago also EUVD-2025-26125 , GHSA-7m47-r75r-cx8v

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

Contao is an Open Source CMS. In versions starting from 5.0.0 and prior to 5.3.38 and 5.6.1, the table access voter in the back end doesn't check if a user is allowed to access the corresponding module. This issue has been patched in versions 5.3.38 and 5.6.1. A workaround involves not relying solely on the voter and additionally to check USER_CAN_ACCESS_MODULE.

Patch / fix

  • packagist contao/core-bundle 5.3.38, 5.6.1
  • packagist contao/contao 5.3.38, 5.6.1
  • contao contao 5.3.38, 5.6.1
  • contao contao_cms 5.3.38, 5.6.1

Is CVE-2025-57758 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist contao/core-bundle
>=5.0.0, <5.3.38
>=5.4.0-RC1, <5.6.1
5.3.38
5.6.1
packagist contao/contao
>=5.0.0, <5.3.38
>=5.4.0-RC1, <5.6.1
5.3.38
5.6.1

Affected products

  • contao contao

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.