# CVE-2024-53386: Stage.js DOM Clobbering vulnerabilty

> Attackers can execute arbitrary JavaScript via DOM clobbering in Stage.js, potentially compromising user sessions or data.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2025
- **Updated:** 3 Mar 2025
- **Also known as:** GHSA-fp3m-g5rc-4c28

## What is CVE-2024-53386?

CVE-2024-53386 is a medium-severity cross-site scripting vulnerability in Piqnt Stage.js, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stage.js through 0.8.10 allows DOM Clobbering (with resultant XSS for untrusted input that contains HTML but does not directly contain JavaScript), because document.currentScript lookup can be shadowed by attacker-injected HTML elements.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-94 (Improper Control of Generation of Code)

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

2 open source packages ship an affected version, including stage-js. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `stage-js` | npm | All versions to 0.8.10 | None |
| `stage-js` | npm | All versions to 0.8.10 | None |

Products: Piqnt Stage.js.

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

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

## Is CVE-2024-53386 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53386 is a medium-severity cross-site scripting vulnerability in Piqnt Stage.js, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53386 exists.

Affected packages and fixed versions:
- stage-js (npm): affected all versions up to 0.8.10; no fix listed
- stage-js (npm): affected all versions up to 0.8.10; 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-53386/ (Markdown: https://insights.sbomify.com/CVE-2024-53386/index.md)
```

## Sources

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

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