# CVE-2023-54409: Frappe before 13.46.1 XSS via html2text Weak Sanitization

> Authenticated attackers can execute arbitrary scripts in victim browsers via insufficiently sanitized HTML input in the Frappe framework.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/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:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-w4rh-867r-qwp3, GHSA-wp7j-3w22-93j6

## What is CVE-2023-54409?

CVE-2023-54409 is a medium-severity cross-site scripting vulnerability in frappe, published on 12 Oct 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

Frappe before 13.46.1 and 14.x before 14.20.0 contains a cross-site scripting vulnerability because the html2text function weakly sanitizes user input. Authenticated attackers can supply crafted HTML that is insufficiently sanitized by html2text, executing scripts in the browsers of users who view the rendered content.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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


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

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

## Is CVE-2023-54409 being exploited?

There is no known exploitation of CVE-2023-54409 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54409 is a medium-severity cross-site scripting vulnerability in frappe, published on 12 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-54409 in the wild and no public exploit code.

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

## Sources

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

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