How severe is GHSA-7f4f-p7mq-p4fv?

No CVSS score has been assigned to GHSA-7f4f-p7mq-p4fv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7f4f-p7mq-p4fv?

GHSA-7f4f-p7mq-p4fv affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-7f4f-p7mq-p4fv?

Update drupal/core to 7.60 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7f4f-p7mq-p4fv is resolved across your whole dependency graph.

How do I detect GHSA-7f4f-p7mq-p4fv 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-7f4f-p7mq-p4fv 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.

How does O3 Security protect against GHSA-7f4f-p7mq-p4fv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7f4f-p7mq-p4fv can be triaged on real exposure rather than presence alone.

Is GHSA-7f4f-p7mq-p4fv actively exploited in the wild?

No public exploit code has been indexed for GHSA-7f4f-p7mq-p4fv 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-7f4f-p7mq-p4fv published, and has it been updated?

GHSA-7f4f-p7mq-p4fv 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

GHSA-7f4f-p7mq-p4fv — drupal/core

GHSA-7f4f-p7mq-p4fv is a security vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.

Drupal External URL injection through URL aliases leading to Open Redirect

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Real-World Exposure

3 pkgs affected

🐘drupal/core🐘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

The path module in Drupal allows users with the 'administer paths' to create pretty URLs for content. In certain circumstances the user can enter a particular path that triggers an open redirect to a malicious url.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 7.0&&< 7.60	7.60`composer require drupal/core:^7.60`
🐘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 7.60 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7f4f-p7mq-p4fv 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7f4f-p7mq-p4fv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-7f4f-p7mq-p4fv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-7f4f-p7mq-p4fv in your dependencies?

O3 Security finds GHSA-7f4f-p7mq-p4fv across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works