CVE-2025-54066VulnerabilityPublished 17 Jul 2025

CVE-2025-54066: DIRACGrid diracx-web · Open Redirect

Affects DIRACGrid diracx-webSource CVE Database V5

Not known to be exploited · CVSS 4.7 Medium : upgrade to 0.1.0-a8 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.1.0-a8

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade diracgrid/diracx-web to 0.1.0-a8.

Affected software

Product	Affected	Fixed in
GitHubdiracgrid/diracx-web`pkg:github/diracgrid/diracx-web`Other threats	Affected <0.1.0-a8	Fixed in 0.1.0-a8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade diracx-web to version 0.1.0-a8 or later, where the vulnerability is fixed by validating and restricting the redirect URI parameter. Until the upgrade is applied, organizations should implement the following mitigations: 1) Employ web application firewalls (WAFs) with rules to detect and block suspicious redirect parameters and parameter pollution attempts targeting diracx-web endpoints. 2) Conduct user awareness training focusing on phishing risks, emphasizing caution when clicking on unexpected or suspicious links, especially those involving authentication workflows. 3) Implement strict Content Security Policy (CSP) headers to restrict the domains to which users can be redirected or loaded from, reducing the risk of malicious redirection. 4) Monitor web server logs for unusual redirect parameter usage patterns and investigate anomalies promptly. 5) If feasible, temporarily disable or restrict the use of the redirect parameter in the application configuration or via custom patches until the official fix is deployed. These targeted actions go beyond generic advice by focusing on the specific vulnerability mechanics and attack vectors.

Description

DiracX-Web is a web application that provides an interface to interact with the DiracX services. Prior to version 0.1.0-a8, an attacker can forge a request that they can pass to redirect an authenticated user to another arbitrary website. In the login page, DiracX-Web has 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, an attacker can hide their malicious URI. This could be used for phishing, and extract new data (such as redirecting to a new "log in" page, and asking another time credentials). Version 0.1.0-a8 fixes this vulnerability.

Impact

For European organizations using diracx-web versions prior to 0.1.0-a8, this vulnerability poses a moderate risk primarily related to phishing and social engineering attacks. Attackers could exploit the open redirect to lure authenticated users into visiting malicious sites that appear trustworthy, potentially leading to credential theft or session hijacking. While the vulnerability itself does not directly compromise system integrity or availability, successful phishing attacks could lead to broader security incidents, including unauthorized access or data breaches. Organizations in sectors with high security requirements, such as finance, healthcare, and critical infrastructure, may face increased risk if attackers leverage this vulnerability as part of multi-stage attacks. Additionally, the use of parameter pollution to hide malicious URLs complicates detection and mitigation efforts. Given the medium CVSS score and the nature of the vulnerability, the direct technical impact is limited, but the indirect consequences through social engineering could be significant.

Summary

CVE-2025-54066 is an open redirect vulnerability (CWE-601) found in the DIRACGrid project’s web application, diracx-web, specifically in versions prior to 0.1.0-a8. DiracX-Web serves as an interface to interact with DiracX services. The vulnerability arises from the login page's handling of a 'redirect' parameter, which specifies the URI to which the user will be redirected after authentication. This parameter is not properly validated or sanitized, allowing an attacker to craft a malicious URL that redirects authenticated users to arbitrary external websites. Furthermore, the vulnerability can be exacerbated by parameter pollution techniques, which can obfuscate the malicious redirect URI, making detection and prevention more difficult. Exploiting this flaw, an attacker could redirect users to phishing sites that mimic legitimate login pages, potentially harvesting additional credentials or sensitive information. The vulnerability does not require authentication to exploit but does require user interaction (clicking on a crafted link). The CVSS v3.1 base score is 4.7 (medium severity), reflecting the network attack vector, low attack complexity, no privileges required, but user interaction needed, and limited impact on confidentiality only. The vulnerability does not affect integrity or availability. The issue was addressed in version 0.1.0-a8 by implementing proper validation of the redirect URI to prevent arbitrary redirection.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Jul 2025, 15:16 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats