# CVE-2024-58390: Frappe before 15.41.0 Privilege Escalation via Document Action

> Authenticated Website Users can escalate privileges to System Manager via improper document action handling in Frappe.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-g6cq-m3m2-c4h3, GHSA-gjqf-v2f6-962h

## What is CVE-2024-58390?

CVE-2024-58390 is a high-severity vulnerability in frappe, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frappe before 14.81.4 and 15.x before 15.41.0 contains an improper privilege management vulnerability involving a certain document action that permits escalation from the Website User role to System Manager. Authenticated attackers with Website User access can combine this document action with additional steps to obtain administrative System Manager privileges in the Frappe application.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-58390 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-58390 is a high-severity vulnerability in frappe, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58390 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-58390/ (Markdown: https://insights.sbomify.com/CVE-2024-58390/index.md)
```

## Sources

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

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