How severe is GHSA-f84q-mgj9-8jfc?

No CVSS score has been assigned to GHSA-f84q-mgj9-8jfc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f84q-mgj9-8jfc?

GHSA-f84q-mgj9-8jfc affects the following packages: drupal/core (Packagist), drupal/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-f84q-mgj9-8jfc?

Update drupal/core to 8.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f84q-mgj9-8jfc is resolved across your whole dependency graph.

How do I detect GHSA-f84q-mgj9-8jfc 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-f84q-mgj9-8jfc 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-f84q-mgj9-8jfc actively exploited in the wild?

No public exploit code has been indexed for GHSA-f84q-mgj9-8jfc 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.

When was GHSA-f84q-mgj9-8jfc published, and has it been updated?

GHSA-f84q-mgj9-8jfc was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Drupal Content moderation Access bypassGHSA-f84q-mgj9-8jfc

GHSA-f84q-mgj9-8jfc is a security vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘drupal/core🐘drupal/core

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

In some conditions, drupal content moderation fails to check a users access to use certain transitions, leading to an access bypass.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.0.0&&< 8.5.8	8.5.8`composer require drupal/core:^8.5.8`
🐘Packagist	`drupal/core`	≥ 8.6.0&&< 8.6.2	8.6.2`composer require drupal/core:^8.6.2`

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 8.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f84q-mgj9-8jfc 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

In some conditions, drupal content moderation fails to check a users access to use certain transitions, leading to an access bypass.

O3 Security · Impact-Aware SCA

Is GHSA-f84q-mgj9-8jfc in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works