# CVE-2024-53384: tsup DOM Clobbering vulnerability

> Attackers can execute arbitrary code via DOM clobbering in tsup, affecting developers using this JavaScript build tool.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2025
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-3mv9-4h5g-vhg3

## What is CVE-2024-53384?

CVE-2024-53384 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A DOM Clobbering vulnerability in tsup v8.3.4 allows attackers to execute arbitrary code via a crafted script in the import.meta.url to document.currentScript in cjs_shims.js components

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tsup` | npm | All versions to 8.3.4 | None |
| `tsup` | npm | All versions to 8.3.4 | None |

Products: Egoist Tsup.

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

No fix has been published for CVE-2024-53384 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-53384 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53384 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53384 exists.

Affected packages and fixed versions:
- tsup (npm): affected all versions up to 8.3.4; no fix listed
- tsup (npm): affected all versions up to 8.3.4; no fix listed

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-53384/ (Markdown: https://insights.sbomify.com/CVE-2024-53384/index.md)
```

## Sources

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

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