CriticalGHSA-8cw5-rv98-5c46CVE-2019-6339DRUPAL-CORE-2019-002

Arbitrary PHP code execution in Drupal

Published 6 Jan 2022 · Updated 10 Dec 2025

Affected packages

Affected
>=7.0.0 <7.62.0
Fixed in
7.62.0
Update to the fixed version for your release line, for example:composer require drupal/drupal:^7.62.0
Affected
>=8.0.0 <8.5.9
Fixed in
8.5.9
Update to the fixed version for your release line, for example:composer require drupal/drupal:^8.5.9
Affected
>=8.6.0 <8.6.6
Fixed in
8.6.6
Update to the fixed version for your release line, for example:composer require drupal/drupal:^8.6.6
drupal/coreComposer
Affected
>=7.0.0 <7.62.0
Fixed in
7.62.0
Update to the fixed version for your release line, for example:composer require drupal/core:^7.62.0
drupal/coreComposer
Affected
>=8.0.0 <8.5.9
Fixed in
8.5.9
Update to the fixed version for your release line, for example:composer require drupal/core:^8.5.9
drupal/coreComposer
Affected
>=8.6.0 <8.6.6
Fixed in
8.6.6
Update to the fixed version for your release line, for example:composer require drupal/core:^8.6.6

Details

In Drupal Core versions 7.x prior to 7.62, 8.6.x prior to 8.6.6, and 8.5.x prior to 8.5.9; A remote code execution vulnerability exists in PHP's built-in phar stream wrapper when performing file operations on an untrusted phar:// URI. Some Drupal code (core, contrib, and custom) may be performing file operations on insufficiently validated user input, thereby being exposed to this vulnerability. This vulnerability is mitigated by the fact that such code paths typically require access to an administrative permission or an atypical configuration.

Is GHSA-8cw5-rv98-5c46 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/drupal, and gives you the command that fixes it.

References

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