# CVE-2026-109621: Frappe ERPNext before 15.120.0 Unauthorized Party Record Access via Permission Bypass

> Authenticated attackers can bypass permission checks to read unauthorized party records in Frappe ERPNext.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-g24j-j8m9-65fg, GHSA-wwgm-3pv3-gmqh

## What is CVE-2026-109621?

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

### Official description

Frappe ERPNext before 15.120.0 and 16.x before 16.23.0 contains an authorization bypass in an endpoint that honours a caller-supplied flag disabling its own permission enforcement. Authenticated attackers can set this flag when calling the endpoint to skip permission checks and read party records beyond their permitted role.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109621 is a high-severity missing authorization vulnerability in frappe erpnext, 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-2026-109621 in the wild and no public exploit code.

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

## Sources

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

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