# CVE-2026-50708: Frappe Framework 17.0.0-dev - Stored XSS in Multi Select Dialog result rendering

> Attackers can inject malicious scripts via the MultiSelectDialog component, potentially leading to session hijacking or code execution in Frappe Framework.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-649m-3hjq-ppg8

## What is CVE-2026-50708?

CVE-2026-50708 is a medium-severity cross-site scripting vulnerability in Frappe Framework, published on 24 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Framework version 17.0.0-dev due to improper neutralization of user-controlled input in the MultiSelectDialog component.

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

## Which versions are affected by CVE-2026-50708?


## How do I fix CVE-2026-50708?

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

## Is CVE-2026-50708 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50708 and fix it if it is affected.

What it is: CVE-2026-50708 is a medium-severity cross-site scripting vulnerability in Frappe Framework, published on 24 Jun 2026. Any signed-in user can exploit it over the network, 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-2026-50708 exists.

Affected product: Frappe Framework. 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-2026-50708/ (Markdown: https://insights.sbomify.com/CVE-2026-50708/index.md)
```

## Sources

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

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