# CVE-2026-130787: Frappe ERPNext before 16.35.0 Missing Authorization in Financial Reporting Endpoints


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-g7r2-v98g-6wcr, GHSA-vmwm-3gc9-c5fh

## What is CVE-2026-130787?

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

### Official description

Frappe ERPNext before 16.35.0 contains a missing authorization vulnerability in financial reporting endpoints that allows low-privilege authenticated users to generate reports outside their permitted scope. Attackers can send crafted requests to affected reporting endpoints to read other companies' tax and payment data, including personal and corporate identifiers and financial totals.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade frappe erpnext to 16.35.0 or later. The advisory says that version fixes it.

## Is CVE-2026-130787 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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