# CVE-2024-58391: Frappe before 15.4.0 XSS via Printview Parameters

> Remote attackers can execute arbitrary scripts in victim browsers via malicious printview URLs in the Frappe framework.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-8v87-5f8f-xgxh, GHSA-v248-pv3c-jvgw

## What is CVE-2024-58391?

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

Frappe before 14.58.0 and 15.x before 15.4.0 contains a cross-site scripting vulnerability in printview because printview parameters are not escaped before being rendered. Remote attackers can craft a malicious printview URL that, when visited by a victim, injects HTML and executes script in the victim's browser session.

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

## Which versions are affected by CVE-2024-58391?


## How do I fix CVE-2024-58391?

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

## Is CVE-2024-58391 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58391 and fix it if it is affected.

What it is: CVE-2024-58391 is a medium-severity cross-site scripting vulnerability in frappe, published on 12 Oct 2026. 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 CVE-2024-58391 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-2024-58391/ (Markdown: https://insights.sbomify.com/CVE-2024-58391/index.md)
```

## Sources

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

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