How severe is GHSA-7cwc-fjqm-8vh8?

No CVSS score has been assigned to GHSA-7cwc-fjqm-8vh8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7cwc-fjqm-8vh8?

GHSA-7cwc-fjqm-8vh8 affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core-recommended (Packagist), drupal/core-recommended (Packagist), drupal/core-recommended (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist), and 1 more. Ecosystems affected: Packagist.

How do I fix GHSA-7cwc-fjqm-8vh8?

Update drupal/core to 10.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cwc-fjqm-8vh8 is resolved across your whole dependency graph.

How do I detect GHSA-7cwc-fjqm-8vh8 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-7cwc-fjqm-8vh8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-7cwc-fjqm-8vh8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7cwc-fjqm-8vh8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7cwc-fjqm-8vh8?

GHSA-7cwc-fjqm-8vh8 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-7cwc-fjqm-8vh8?

GHSA-7cwc-fjqm-8vh8 is classified as CWE-178 (CWE-178), CWE-289 (CWE-289). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7cwc-fjqm-8vh8 published, and has it been updated?

GHSA-7cwc-fjqm-8vh8 was published on December 10, 2024 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-7cwc-fjqm-8vh8: drupal/core

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7cwc-fjqm-8vh8.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

9 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/drupal🐘drupal/drupal+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.0.0&&< 10.2.11	10.2.11`composer require drupal/core:^10.2.11`
🐘Packagist	`drupal/core`	≥ 10.3.0&&< 10.3.9	10.3.9`composer require drupal/core:^10.3.9`
🐘Packagist	`drupal/core`	≥ 11.0.0&&< 11.0.8	11.0.8`composer require drupal/core:^11.0.8`
🐘Packagist	`drupal/core-recommended`	≥ 8.0.0&&< 10.2.11	10.2.11`composer require drupal/core-recommended:^10.2.11`
🐘Packagist	`drupal/core-recommended`	≥ 10.3.0&&< 10.3.9	10.3.9`composer require drupal/core-recommended:^10.3.9`
🐘Packagist	`drupal/core-recommended`	≥ 11.0.0&&< 11.0.8	11.0.8`composer require drupal/core-recommended:^11.0.8`

Affected Products

1 product · 3 configurations

Application

drupaldrupal

≥ 11.0.0 && < 11.0.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 10.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cwc-fjqm-8vh8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-7cwc-fjqm-8vh8 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

GHSA-7cwc-fjqm-8vh8 — drupal/core