# CVE-2026-124315: Frappe ERPNext before 15.121.4 and 16.36.0 Missing Authorization via get_bom_items


- **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
- **Fix available:** No
- **Published:** 7 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-66vp-2c6m-m4r6, GHSA-w587-ghqf-6jpp

## What is CVE-2026-124315?

CVE-2026-124315 is a high-severity vulnerability in frappe erpnext, published on 7 Nov 2026. 

### Official description

Frappe ERPNext before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in the whitelisted get_bom_items and get_bom_diff methods that skip BOM read permission checks. Any authenticated user, including portal or no-role users, can call get_bom_items with a BOM name to retrieve every raw material, quantity, rate and cost.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-124315 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124315 is a high-severity vulnerability in frappe erpnext, published on 7 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124315 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-124315/ (Markdown: https://insights.sbomify.com/CVE-2026-124315/index.md)
```

## Sources

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

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