CVE-2019-10642: Contao CSRF Token Bypass

CVE-2019-10642 · Severity: low · CVSS 3 · Published 2022-05-14

Contao CSRF Token Bypass

Technologies: contao/contao (Packagist), contao/core-bundle (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2019-10642 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-10642 being exploited in the wild.
How severe is CVE-2019-10642?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
contao/contao (Packagist) ECOSYSTEM:introduced=4.7.0,fixed=4.7.3; contao/core-bundle (Packagist) ECOSYSTEM:introduced=4.7.0,fixed=4.7.3.
Is there a fix for CVE-2019-10642?
Yes. contao/contao (Packagist): upgrade to 4.7.3 or later; contao/core-bundle (Packagist): upgrade to 4.7.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-10642?
Check whether you run contao/contao (Packagist) or contao/core-bundle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • contao/contao (Packagist): upgrade to 4.7.3 or later
    composer require contao/contao:^4.7.3
  • contao/core-bundle (Packagist): upgrade to 4.7.3 or later
    composer require contao/core-bundle:^4.7.3

Affected products

  • contao/contao (Packagist) ECOSYSTEM:introduced=4.7.0,fixed=4.7.3
  • contao/core-bundle (Packagist) ECOSYSTEM:introduced=4.7.0,fixed=4.7.3

Identifiers

  • CVE-2019-10642
  • GHSA-hwmh-9jj9-8c9c

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.