Contao CSRF Token Bypass

published 2019-04-17 7y ago modified 2026-06-17 4mo ago also GHSA-hwmh-9jj9-8c9c , EUVD-2022-4230

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits: 0; none known

Contao 4.7 allows CSRF.

Patch / fix

fixed in 2 links 1

packagist contao/contao 4.7.3
packagist contao/core-bundle 4.7.3

github.com/contao/contao@ee2c813 commit

Is CVE-2019-10642 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

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	contao/contao	>=4.7.0, <4.7.3	4.7.3
packagist	contao/core-bundle	>=4.7.0, <4.7.3	4.7.3

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

github.com /contao/contao/commit/ee2c8130c2e68a1d0d2e75bd6b774c4393942b15
web
contao.org /en/news.html
web, vendor-advisory
contao.org /en/news/security-vulnerability-cve-2019-10642.html
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2019-10642
advisory
github.com /FriendsOfPHP/security-advisories/blob/master/contao/contao/CVE-2019-10642.yaml
web
github.com /FriendsOfPHP/security-advisories/blob/master/contao/core-bundle/CVE-2019-10642.yaml
web
github.com /contao/contao
package

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.