CriticalGHSA-7fh9-933g-885pCVE-2018-7600DRUPAL-CORE-2018-002

Drupal Core Remote Code Execution Vulnerability

Published 14 May 2022 · Updated 10 Dec 2025

Affected packages

drupal/coreComposer
Affected
>=7.0 <7.58
Fixed in
7.58
Update to the fixed version for your release line, for example:composer require drupal/core:^7.58
drupal/coreComposer
Affected
>=8.0 <8.3.9
Fixed in
8.3.9
Update to the fixed version for your release line, for example:composer require drupal/core:^8.3.9
drupal/coreComposer
Affected
>=8.4.0 <8.4.6
Fixed in
8.4.6
Update to the fixed version for your release line, for example:composer require drupal/core:^8.4.6
drupal/coreComposer
Affected
>=8.5.0 <8.5.1
Fixed in
8.5.1
Update to the fixed version for your release line, for example:composer require drupal/core:^8.5.1
Affected
>=7.0 <7.58
Fixed in
7.58
Update to the fixed version for your release line, for example:composer require drupal/drupal:^7.58
Affected
>=8.0 <8.3.9
Fixed in
8.3.9
Update to the fixed version for your release line, for example:composer require drupal/drupal:^8.3.9
Affected
>=8.4 <8.4.6
Fixed in
8.4.6
Update to the fixed version for your release line, for example:composer require drupal/drupal:^8.4.6
Affected
>=8.5 <8.5.1
Fixed in
8.5.1
Update to the fixed version for your release line, for example:composer require drupal/drupal:^8.5.1

Details

Drupal before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1 allows remote attackers to execute arbitrary code because of an issue affecting multiple subsystems with default or common module configurations.

Is GHSA-7fh9-933g-885p in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.