GHSA-hfj7-542q-8fvv is a medium-severity (CVSS 4.7) Open Redirect vulnerability in @dirac-grid/diracx-web-components. A fix is available for @dirac-grid/diracx-web-components — see the affected versions and patch details below.
DiracX-Web is vulnerable to attack through an Open Redirect on its login page
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-hfj7-542q-8fvv.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-hfj7-542q-8fvv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@dirac-grid/diracx-web-componentsnpmDescription
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
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @dirac-grid/diracx-web-components | all versions | 0.1.0-a8npm install @dirac-grid/diracx-web-components@0.1.0-a8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @dirac-grid/diracx-web-components, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hfj7-542q-8fvv can be triaged on real exposure rather than presence alone.
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
Is GHSA-hfj7-542q-8fvv in your dependencies?
O3 Security finds GHSA-hfj7-542q-8fvv across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.