CVE-2025-54793
BaseFortify
Publication date: 2025-08-08
Last updated on: 2025-11-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| astro | astro | From 5.2.0 (inc) to 5.12.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-601 | The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an Open Redirect issue in the Astro web framework versions 5.2.0 through 5.12.7. It occurs in the trailing slash redirection logic when handling paths with double slashes. An attacker can craft URLs with double slashes that cause the site to redirect users to arbitrary external domains, such as https://mydomain.com//malicious-site.com/. This can be exploited to redirect users to malicious sites.
How can this vulnerability impact me? :
This vulnerability can increase the risk of phishing and other social engineering attacks by allowing attackers to redirect users to malicious external websites. Users may be tricked into trusting these redirects, potentially leading to credential theft, malware infection, or other security compromises.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring HTTP responses for redirect Location headers that start with double slashes (//), which indicate potential open redirect attempts. You can use network traffic inspection tools or web server logs to identify such responses. For example, using command-line tools like curl to test URLs with double slashes and observe the Location header in the response can help detect the issue. Example command: curl -I https://yourdomain.com//malicious-site.com/ and check if the Location header redirects to an external domain starting with //.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading Astro to version 5.12.8 or later where the vulnerability is fixed. If upgrading is not immediately possible, implement a network-level workaround by blocking outgoing HTTP redirect responses with a Location header value that starts with double slashes (//) to prevent redirection to arbitrary external domains.