# CVE-2023-5718: Information disclosure in Vue.js devtools

> A malicious web page can steal sensitive screenshot data from the Vue.js Devtools extension via postMessage, exposing local or sensitive resources.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Oct 2023
- **Updated:** 11 Sep 2024
- **Also known as:** GHSA-hch9-gprw-2g9j

## What is CVE-2023-5718?

CVE-2023-5718 is a medium-severity vulnerability in Vue.js devtools, published on 23 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Vue.js Devtools extension was found to leak screenshot data back to a malicious web page via the standard `postMessage()` API. By creating a malicious web page with an iFrame targeting a sensitive resource (i.e. a locally accessible file or sensitive website), and registering a listener on the web page, the extension sent messages back to the listener, containing the base64 encoded screenshot data of the sensitive resource.

Weakness: CWE-346 (Origin Validation Error), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-5718?

It affects 1 product.


Products: Vuejs Devtools.

## How do I fix CVE-2023-5718?

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

## Is CVE-2023-5718 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5718 and fix it if it is affected.

What it is: CVE-2023-5718 is a medium-severity vulnerability in Vue.js devtools, published on 23 Oct 2023. An attacker can exploit it over the internet without logging in, 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-2023-5718 exists.

Affected product: Vue.js devtools. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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