NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

DiracX-Web is vulnerable to attack through an Open Redirect on its login pageGHSA-hfj7-542q-8fvv

MEDIUMFix: DIRACGrid/diracx-web@eba3b7b

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.

Also known asCVE-2025-54066
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk
0.00%0.30%0.61%0.91%0.0%0.4%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@dirac-grid/diracx-web-componentsnpm
32downloads / 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
EcosystemPackageVulnerable rangeFix
📦npm@dirac-grid/diracx-web-componentsall versions0.1.0-a8npm install @dirac-grid/diracx-web-components@0.1.0-a8

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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.

  3. Workarounds

    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
DiracX-Web is vulnerable to attack through an Open…