MediumGHSA-7cwc-fjqm-8vh8BIT-drupal-2024-55634CVE-2024-55634DRUPAL-CORE-2024-004

Drupal core Access bypass

Published 10 Dec 2024 · Updated 10 Dec 2025

Affected packages

drupal/coreComposer
Affected
>=8.0.0 <10.2.11
Fixed in
10.2.11
Update to the fixed version for your release line, for example:composer require drupal/core:^10.2.11
drupal/coreComposer
Affected
>=10.3.0 <10.3.9
Fixed in
10.3.9
Update to the fixed version for your release line, for example:composer require drupal/core:^10.3.9
drupal/coreComposer
Affected
>=11.0.0 <11.0.8
Fixed in
11.0.8
Update to the fixed version for your release line, for example:composer require drupal/core:^11.0.8
Affected
>=8.0.0 <10.2.11
Fixed in
10.2.11
Update to the fixed version for your release line, for example:composer require drupal/core-recommended:^10.2.11
Affected
>=10.3.0 <10.3.9
Fixed in
10.3.9
Update to the fixed version for your release line, for example:composer require drupal/core-recommended:^10.3.9
Affected
>=11.0.0 <11.0.8
Fixed in
11.0.8
Update to the fixed version for your release line, for example:composer require drupal/core-recommended:^11.0.8
Affected
>=8.0.0 <10.2.11
Fixed in
10.2.11
Update to the fixed version for your release line, for example:composer require drupal/drupal:^10.2.11
Affected
>=10.3.0 <10.3.9
Fixed in
10.3.9
Update to the fixed version for your release line, for example:composer require drupal/drupal:^10.3.9
Affected
>=11.0.0 <11.0.8
Fixed in
11.0.8
Update to the fixed version for your release line, for example:composer require drupal/drupal:^11.0.8

Details

Drupal's uniqueness checking for certain user fields is inconsistent depending on the database engine and its collation. As a result, a user may be able to register with the same email address as another user. This may lead to data integrity issues. This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

Is GHSA-7cwc-fjqm-8vh8 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.