# GHSA-9xr8-8hmc-389f: Cross-Site Scripting in vant

> Attackers can execute arbitrary JavaScript in victims' browsers via unsanitized text in the Picker component of the vant library.

- **Severity:** Not scored
- **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:** Yes
- **Published:** 22 Nov 2019

## What is GHSA-9xr8-8hmc-389f?

GHSA-9xr8-8hmc-389f is a cross-site scripting vulnerability in vant, published on 22 Nov 2019. 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

Versions of `vant` prior to 2.1.8 are vulnerable to Cross-Site Scripting. The text value of the `Picker` component column is not sanitized, which may allow attackers to execute arbitrary JavaScript in a victim's browser.

## Recommendation

Upgrade to version 2.1.8 or later.

## Which versions are affected by GHSA-9xr8-8hmc-389f?

2 open source packages ship an affected version, including vant.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vant` | npm | All versions | 2.1.8 |
| `vant` | npm | All versions | 2.1.8 |

## How do I fix GHSA-9xr8-8hmc-389f?

Upgrade vant to 2.1.8 or later.

## Is GHSA-9xr8-8hmc-389f being exploited?

There is no known exploitation of GHSA-9xr8-8hmc-389f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9xr8-8hmc-389f and fix it if it is affected.

What it is: GHSA-9xr8-8hmc-389f is a cross-site scripting vulnerability in vant, published on 22 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-9xr8-8hmc-389f in the wild and no public exploit code.

Affected packages and fixed versions:
- vant (npm): affected all versions; fixed in 2.1.8
- vant (npm): affected all versions; fixed in 2.1.8

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/GHSA-9xr8-8hmc-389f/ (Markdown: https://insights.sbomify.com/GHSA-9xr8-8hmc-389f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9xr8-8hmc-389f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9xr8-8hmc-389f/
Summaries are generated and may contain mistakes; the official description above is the record.