# CVE-2024-6783: Vue client-side XSS via prototype pollution

> Attackers can execute arbitrary JavaScript in Vue applications by exploiting prototype pollution to modify static class or style properties.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2024
- **Updated:** 30 Aug 2024
- **Also known as:** CLSA-2026-1774830273, CLSA-2026-1789477857, CLSA-2026-1792340315, CLSA-2026-1793148257, CLSA-2026-1793148263, GHSA-g3ch-rx76-35fx

## What is CVE-2024-6783?

CVE-2024-6783 is a medium-severity cross-site scripting vulnerability in vue, published on 23 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been discovered in Vue, that allows an attacker to perform XSS via prototype pollution. The attacker could change the prototype chain of some properties such as `Object.prototype.staticClass` or `Object.prototype.staticStyle` to execute arbitrary JavaScript code.

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

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

2 open source packages ship an affected version, including vue-template-compiler.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vue-template-compiler` | npm | From 2.0.0 | None |
| `vue-template-compiler` | npm | From 2.0.0 | None |

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

Upgrade to a fixed version.

## Is CVE-2024-6783 being exploited?

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

Public exploit code:

- CVE-2024-6783 - Vue CVE (github_poc): https://github.com/HORKimhab/CVE-2024-6783

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6783 is a medium-severity cross-site scripting vulnerability in vue, published on 23 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6783 exists.

Affected packages and fixed versions:
- vue-template-compiler (npm): affected from 2.0.0; no fix listed
- vue-template-compiler (npm): affected from 2.0.0; 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-6783/ (Markdown: https://insights.sbomify.com/CVE-2024-6783/index.md)
```

## Sources

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

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