Is CVE-2018-7602 exploited in the wild?

Yes. CVE-2018-7602 is known to be exploited in the wild, first recorded on 13 April 2022. Treat it as urgent.

How severe is CVE-2018-7602?

Critical severity, with a CVSS score of 3.1, published 23 April 2024.

Which products and versions are affected?

drupal/core (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.59, ECOSYSTEM:introduced=8.0.0,fixed=8.4.8|ECOSYSTEM:introduced=8.5.0,fixed=8.5.3; drupal/drupal (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.59.

Is there a fix for CVE-2018-7602?

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

How is CVE-2018-7602 attacked?

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

Am I affected by CVE-2018-7602?

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-7602: Drupal Core Remote Code Execution Vulnerability

CVE-2018-7602 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2024-04-23

A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. Attackers can exploit multiple attack vectors to compromise the site, a flaw related to the previous SA-CORE-2018-002 (Drupalgeddon 2) vulnerability.

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

Quick answers

Is CVE-2018-7602 exploited in the wild?: Yes. CVE-2018-7602 is known to be exploited in the wild, first recorded on 13 April 2022. Treat it as urgent.
How severe is CVE-2018-7602?: Critical severity, with a CVSS score of 3.1, published 23 April 2024.
Which products and versions are affected?: drupal/core (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.59, ECOSYSTEM:introduced=8.0.0,fixed=8.4.8|ECOSYSTEM:introduced=8.5.0,fixed=8.5.3; drupal/drupal (Packagist) ECOSYSTEM:introduced=7.0,fixed=7.59.
Is there a fix for CVE-2018-7602?: Yes. drupal/core (Packagist): upgrade to 7.59, 8.4.8 or later; drupal/drupal (Packagist): upgrade to 7.59 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2018-7602 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2018-7602?: 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.59, 8.4.8 or later
```
composer require drupal/core:^8.4.8
```
drupal/drupal (Packagist): upgrade to 7.59 or later
```
composer require drupal/drupal:^7.59
```

Affected products

Drupal Drupal Core 7.x, 8.x (specifically < 7.59, 8.4.x < 8.4.8, 8.5.x < 8.5.3)

Identifiers

CVE-2018-7602
DRUPAL-CORE-2018-004
GHSA-297x-j9pm-xjgg

Timeline

2018-04-25: disclosed: SA-CORE-2018-004 / CVE-2018-7602 published by Drupal.org
2018-04-25: patched: Security updates released for Drupal 7.59, 8.4.8, and 8.5.3
2022-04-13: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
2018-04-25: exploited: Reported as being exploited in the wild at the time of disclosure.

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