How severe is GHSA-hfj7-542q-8fvv?

GHSA-hfj7-542q-8fvv has a CVSS score of 4.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hfj7-542q-8fvv?

GHSA-hfj7-542q-8fvv affects the following packages: @dirac-grid/diracx-web-components (npm). Ecosystems affected: npm.

How do I fix GHSA-hfj7-542q-8fvv?

Update @dirac-grid/diracx-web-components to 0.1.0-a8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfj7-542q-8fvv is resolved across your whole dependency graph.

How do I detect GHSA-hfj7-542q-8fvv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @dirac-grid/diracx-web-components. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hfj7-542q-8fvv 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-hfj7-542q-8fvv?

O3 pinpoints whether GHSA-hfj7-542q-8fvv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hfj7-542q-8fvv actively exploited in the wild?

No public exploit code has been indexed for GHSA-hfj7-542q-8fvv 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-hfj7-542q-8fvv?

GHSA-hfj7-542q-8fvv has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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-hfj7-542q-8fvv?

GHSA-hfj7-542q-8fvv is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hfj7-542q-8fvv published, and has it been updated?

GHSA-hfj7-542q-8fvv was published on July 17, 2025 and was last updated on July 17, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-hfj7-542q-8fvv

MEDIUM

DiracX-Web is vulnerable to attack through an Open Redirect on its login page

Also known asCVE-2025-54066

Published

Jul 17, 2025

Updated

Jul 17, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk25th percentile+0.15%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@dirac-grid/diracx-web-componentsnpm

28downloads / week

Description

Summary

An attacker can forge a request to redirect an authenticated user to any arbitrary website.

Details

On the login page, we have a redirect field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI.

Paired with a parameter pollution, we can hide our malicious URI (ex: https://dns.com/?param1=im_hidden_if_theres_lot_of_args?param1=bbb).

PoC

https://diracx-cert.app.cern.ch/auth?redirect=https://ipcim.com/en/where/?dsdsd=qsqsfsjfnsfniizaeiaapzqlalkqkaizqqijsjaopmqmxna?redirect=https://diracx-cert-app.cern.ch/auth

This POC can leak user's position.

Impact

This could be used for phishing and extracting new data (such as redirecting to a new "log in" page, and asking users to reenter credentials).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@dirac-grid/diracx-web-components`	all versions	0.1.0-a8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @dirac-grid/diracx-web-components. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @dirac-grid/diracx-web-components to 0.1.0-a8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfj7-542q-8fvv 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 pinpoints whether GHSA-hfj7-542q-8fvv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hfj7-542q-8fvv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An attacker can forge a request to redirect an authenticated user to any arbitrary website. ### Details On the login page, we have a `redirect` field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI. Paired with a parameter pollution, we can hide our malicious URI (ex: `https://dns.com/?param1=im_hidden_if_theres_lot_of_args?param1=bbb`). ### PoC https://diracx-cert.app.cern.ch/auth?redirect=https://ipcim.com/en/where/?dsdsd=qsqsfsjfnsfniizaeiaapzqlalkqkaizqqijsjaopmqmxna?redirect=https://diracx-cert-app.cern

O3 Security · Impact-Aware SCA

Is GHSA-hfj7-542q-8fvv in your dependencies?

O3 detects GHSA-hfj7-542q-8fvv across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works