p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de astro · Página 2

Vulnerabilidades publicadas para astro en los últimos 30 días: 2. Incluidas en el catálogo KEV: 0.

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 29

  1. CVE-2025-64745

    Baja · CVSS 2.7EPSS 0,26%Corrección disponible

    Astro development server error page vulnerable to reflected Cross-site Scripting

    Astro is a web framework. Starting in version 5.2.0 and prior to version 5.15.6, a Reflected Cross-Site Scripting (XSS) vulnerability exists in Astro's development server error pages when the `trailingSlash` configuration option is used. An attacker can inject arbitrary JavaScript code that executes in the victim's browser context by crafting a malicious URL. While this vulnerability only affects the development server and not production builds, it could be exploited to compromise developer environments through social engineering or malicious links. Version 5.15.6 fixes the issue.

    • Actualiza a 5.15.6
    Publicación Actualización
  2. CVE-2025-64525

    Media · CVSS 6.5EPSS 1,24%Código de explotación públicoCorrección disponible

    Astro: URL manipulation via unsanitized headers leads to path-based middleware protections bypass, potential SSRF/cache-poisoning, CVE-2025-61925 bypass

    Astro is a web framework. In Astro versions 2.16.0 up to but excluding 5.15.5 which utilizeon-demand rendering, request headers `x-forwarded-proto` and `x-forwarded-port` are insecurely used, without sanitization, to build the URL. This has several consequences, the most important of which are: middleware-based protected route bypass (only via `x-forwarded-proto`), DoS via cache poisoning (if a CDN is present), SSRF (only via `x-forwarded-proto`), URL pollution (potential SXSS, if a CDN is present), and WAF bypass. Version 5.15.5 contains a patch.

    • Actualiza a 5.15.5
    Publicación Actualización
  3. CVE-2025-59837

    Alta · CVSS 7.2EPSS 0,35%Corrección disponible

    astro allows bypass of image proxy domain validation leading to SSRF and potential XSS

    Astro is a web framework that includes an image proxy. In versions 5.13.4 and later before 5.13.10, the image proxy domain validation can be bypassed by using backslashes in the href parameter, allowing server-side requests to arbitrary URLs. This can lead to server-side request forgery (SSRF) and potentially cross-site scripting (XSS). This vulnerability exists due to an incomplete fix for CVE-2025-58179. Fixed in 5.13.10.

    • Actualiza a 5.13.10
    Publicación Actualización
  4. CVE-2025-61925

    Media · CVSS 6.5EPSS 0,41%Corrección disponible

    Astro's `X-Forwarded-Host` is reflected with no validation

    Astro is a web framework. Prior to version 5.14.2, Astro reflects the value in `X-Forwarded-Host` in output when using `Astro.url` without any validation. It is common for web servers such as nginx to route requests via the `Host` header, and forward on other request headers. As such as malicious request can be sent with both a `Host` header and an `X-Forwarded-Host` header where the values do not match and the `X-Forwarded-Host` header is malicious. Astro will then return the malicious value. This could result in any usages of the `Astro.url` value in code being manipulated by a request. For example if a user follows guidance and uses `Astro

    • Actualiza a 5.14.3
    Publicación Actualización
  5. CVE-2025-55303

    Media · CVSS 6.9EPSS 0,64%Código de explotación públicoCorrección disponible

    Unauthorized third-party images in Astro’s _image endpoint

    Astro is a web framework for content-driven websites. In versions of astro before 5.13.2 and 4.16.18, the image optimization endpoint in projects deployed with on-demand rendering allows images from unauthorized third-party domains to be served. On-demand rendered sites built with Astro include an /_image endpoint which returns optimized versions of images. A bug in impacted versions of astro allows an attacker to bypass the third-party domain restrictions by using a protocol-relative URL as the image source, e.g. /_image?href=//example.com/image.png. This vulnerability is fixed in 5.13.2 and 4.16.18.

    • Actualiza a 4.16.19
    • Actualiza a 5.13.2
    Publicación Actualización
  6. CVE-2025-54793

    Media · CVSS 5.5EPSS 0,65%Código de explotación públicoCorrección disponible

    Astro: Duplicate trailing slash feature can lead to Open Redirects

    Astro is a web framework for content-driven websites. In versions 5.2.0 through 5.12.7, there is an Open Redirect vulnerability in the trailing slash redirection logic when handling paths with double slashes. This allows an attacker to redirect users to arbitrary external domains by crafting URLs such as https://mydomain.com//malicious-site.com/. This increases the risk of phishing and other social engineering attacks. This affects sites that use on-demand rendering (SSR) with the Node or Cloudflare adapters. It does not affect static sites, or sites deployed to Netlify or Vercel. This issue is fixed in version 5.12.8. To work around this iss

    • Actualiza a 5.12.8
    Publicación Actualización
  7. CVE-2024-56159

    Alta · CVSS 7.8EPSS 1,54%Código de explotación públicoCorrección disponible

    Server source code is exposed to the public if sourcemaps are enabled

    Astro is a web framework for content-driven websites. A bug in the build process allows any unauthenticated user to read parts of the server source code. During build, along with client assets such as css and font files, the sourcemap files **for the server code** are moved to a publicly-accessible folder. Any outside party can read them with an unauthorized HTTP GET request to the same server hosting the rest of the website. While some server files are hashed, making their access obscure, the files corresponding to the file system router (those in `src/pages`) are predictably named. For example. the sourcemap file for `src/pages/index.astro`

    • Actualiza a 4.16.18
    • Actualiza a 5.0.8
    Publicación Actualización
  8. CVE-2024-56140

    Media · CVSS 5.9EPSS 0,22%Corrección disponible

    Bypass of CSRF Middleware in Astro

    Astro is a web framework for content-driven websites. In affected versions a bug in Astro’s CSRF-protection middleware allows requests to bypass CSRF checks. When the `security.checkOrigin` configuration option is set to `true`, Astro middleware will perform a CSRF check. However, a vulnerability exists that can bypass this security. A semicolon-delimited parameter is allowed after the type in `Content-Type`. Web browsers will treat a `Content-Type` such as `application/x-www-form-urlencoded; abc` as a `simple request` and will not perform preflight validation. In this case, CSRF is not blocked as expected. Additionally, the `Content-Type` he

    • Actualiza a 4.16.17
    Publicación Actualización
  9. CVE-2024-47885

    Media · CVSS 5.9EPSS 0,45%Corrección disponible

    astro's client-side router has DOM Clobbering Gadget that leads to XSS

    The Astro web framework has a DOM Clobbering gadget in the client-side router starting in version 3.0.0 and prior to version 4.16.1. It can lead to cross-site scripting (XSS) in websites enables Astro's client-side routing and has *stored* attacker-controlled scriptless HTML elements (i.e., `iframe` tags with unsanitized `name` attributes) on the destination pages. This vulnerability can result in cross-site scripting (XSS) attacks on websites that built with Astro that enable the client-side routing with `ViewTransitions` and store the user-inserted scriptless HTML tags without properly sanitizing the `name` attributes on the page. Version 4

    • Actualiza a 4.16.1
    Publicación Actualización

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →