# CVE-2024-47885: astro's client-side router has DOM Clobbering Gadget that leads to XSS

> Attackers can execute arbitrary JavaScript via DOM clobbering in Astro's client-side router if ViewTransitions are enabled and user HTML is unsanitized.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Oct 2024
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-m85w-3h95-hcf9

## What is CVE-2024-47885?

CVE-2024-47885 is a medium-severity cross-site scripting vulnerability in withastro astro, published on 14 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.16.1 contains a patch for this issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-47885?

2 open source packages ship an affected version, including astro. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `astro` | npm | From 3.0.0 | 4.16.1 |
| `astro` | npm | From 3.0.0 | 4.16.1 |

Products: Astro Astro.

## How do I fix CVE-2024-47885?

Upgrade astro to 4.16.1 or later.

## Is CVE-2024-47885 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47885 exists.

## Other vulnerabilities in withastro astro

- [CVE-2024-56159](https://insights.sbomify.com/CVE-2024-56159/): Server source code is exposed to the public if sourcemaps are enabled (high 7.8)
- [CVE-2026-54299](https://insights.sbomify.com/CVE-2026-54299/): Astro: Host header SSRF in prerendered error page fetch (high 7.5)
- [CVE-2025-59837](https://insights.sbomify.com/CVE-2025-59837/): astro allows bypass of image proxy domain validation leading to SSRF and potential XSS (high 7.2)
- [CVE-2026-50146](https://insights.sbomify.com/CVE-2026-50146/): Astro: Reflected XSS via unescaped slot name (high 7.1)
- [CVE-2025-64764](https://insights.sbomify.com/CVE-2025-64764/): Astro is vulnerable to Reflected XSS via the server islands feature (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47885 and fix it if it is affected.

What it is: CVE-2024-47885 is a medium-severity cross-site scripting vulnerability in withastro astro, published on 14 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47885 exists.

Affected packages and fixed versions:
- astro (npm): affected from 3.0.0; fixed in 4.16.1
- astro (npm): affected from 3.0.0; fixed in 4.16.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47885/ (Markdown: https://insights.sbomify.com/CVE-2024-47885/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47885
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47885
- OSV: https://osv.dev/vulnerability/CVE-2024-47885

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47885/
Summaries are generated and may contain mistakes; the official description above is the record.