Is CVE-2018-7600 exploited in the wild?

Yes. CVE-2018-7600 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.

How severe is CVE-2018-7600?

Critical severity, with a CVSS score of 3, published 14 May 2022.

Which products and versions are affected?

drupal/core (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.58, ECOSYSTEM:introduced=8.0.0,fixed=8.3.9|ECOSYSTEM:introduced=8.4.0,fixed=8.4.6|ECOSYSTEM:introduced=8.5.0,fixed=8.5.1; drupal/drupal (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.58.

Is there a fix for CVE-2018-7600?

Yes. drupal/core (Packagist): upgrade to 7.58, 8.3.9 or later; drupal/drupal (Packagist): upgrade to 7.58 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2018-7600 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2018-7600?

Check whether you run Drupal Core, drupal/core (Packagist) or drupal/drupal (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.

CVE-2018-7600: Drupal Core Remote Code Execution Vulnerability

CVE-2018-7600 · Severity: critical · CVSS 3 · Exploited in the wild · Published 2022-05-14

Drupal Core contains a remote code execution vulnerability due to improper input validation in multiple subsystems. An unauthenticated remote attacker can exploit this to execute arbitrary code and achieve complete site compromise.

Technologies: Drupal Core, drupal/core (Packagist), drupal/drupal (Packagist). Vendors: Drupal, Packagist.

Quick answers

Is CVE-2018-7600 exploited in the wild?: Yes. CVE-2018-7600 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2018-7600?: Critical severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?: drupal/core (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.58, ECOSYSTEM:introduced=8.0.0,fixed=8.3.9|ECOSYSTEM:introduced=8.4.0,fixed=8.4.6|ECOSYSTEM:introduced=8.5.0,fixed=8.5.1; drupal/drupal (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.58.
Is there a fix for CVE-2018-7600?: Yes. drupal/core (Packagist): upgrade to 7.58, 8.3.9 or later; drupal/drupal (Packagist): upgrade to 7.58 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2018-7600 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2018-7600?: Check whether you run Drupal Core, drupal/core (Packagist) or drupal/drupal (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

drupal/core (Packagist): upgrade to 7.58, 8.3.9 or later
```
composer require drupal/core:^8.3.9
```
drupal/drupal (Packagist): upgrade to 7.58 or later
```
composer require drupal/drupal:^7.58
```

Affected products

Drupal Drupal Core before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1

Identifiers

CVE-2018-7600
DRUPAL-CORE-2018-002
GHSA-7fh9-933g-885p

Timeline

2018-03-28: advisory: Drupal security advisory SA-CORE-2018-002 published.
2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.

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