# CVE-2023-51219: Cross-site scripting in n/a

> Attackers can execute JavaScript via deep links to steal access tokens, enabling account takeover and chat message reading in KakaoTalk.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 3 Jun 2024
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-g545-rmg6-689p

## What is CVE-2023-51219?

CVE-2023-51219 is a critical cross-site scripting vulnerability in n/a, published on 3 Jun 2024. 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

A deep link validation issue in KakaoTalk 10.4.3 allowed a remote adversary to direct users to run any attacker-controlled JavaScript within a WebView. The impact was further escalated by triggering another WebView that leaked its access token in a HTTP request header. Ultimately, this access token could be used to take over another user's account and read her/his chat messages.

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

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


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

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

## Is CVE-2023-51219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51219 is a critical cross-site scripting vulnerability in n/a, published on 3 Jun 2024. 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-51219 exists.

Affected product: n/a. 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-51219/ (Markdown: https://insights.sbomify.com/CVE-2023-51219/index.md)
```

## Sources

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

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