# CVE-2026-3673: Frappe Framework 16.10.0 - Stored DOM XSS in Tag Pill Renderer

> An authenticated attacker can execute arbitrary JavaScript in a victim's browser by storing malicious tags in the Frappe Framework.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-qg6x-fw6m-9qrp

## What is CVE-2026-3673?

CVE-2026-3673 is a medium-severity cross-site scripting vulnerability in Frappe, published on 22 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An authenticated attacker can store a crafted tag value in _user_tags and trigger JavaScript execution when a victim opens the list/report view where tags are rendered. The vulnerable renderer interpolates tag content into HTML attributes and element content without escaping.
This issue affects Frappe: 16.10.10.

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

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

It affects 1 product.


Products: Frappe Frappe.

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

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

## Is CVE-2026-3673 being exploited?

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

## Other vulnerabilities in Frappe

- [CVE-2019-14965](https://insights.sbomify.com/CVE-2019-14965/): Code injection in n/a (critical 9.8)
- [CVE-2026-35614](https://insights.sbomify.com/CVE-2026-35614/): Frappe has a SQL injection in bulk_update (critical 9.3)
- [CVE-2026-31877](https://insights.sbomify.com/CVE-2026-31877/): Frappe SQL Injection due to improper field sanitization (critical 9.3)
- [CVE-2025-68929](https://insights.sbomify.com/CVE-2025-68929/): Frappe may be vulnerable remote code execution due to server-side template injection (critical 9.1)
- [CVE-2019-14966](https://insights.sbomify.com/CVE-2019-14966/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3673 is a medium-severity cross-site scripting vulnerability in Frappe, published on 22 Apr 2026. An attacker needs administrator access to exploit it, 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-3673 exists.

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

## Sources

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

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