# CVE-2026-96672: Frappe ERPNext before 16.34.1 Unauthorized Method Invocation

> Accounts Managers can invoke arbitrary internal server-side methods via Financial Report Templates, leading to code execution and data disclosure.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/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:** 23 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-794x-fhm7-58j7, GHSA-vjc2-5pxv-9jpv

## What is CVE-2026-96672?

CVE-2026-96672 is a medium-severity code injection vulnerability in Frappe ERPNext, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frappe ERPNext versions before 16.34.1 fail to validate that Financial Report Template calculation_formula values reference whitelisted methods before passing them to frappe.call(). Accounts Managers can supply arbitrary dotted Python paths to invoke non-whitelisted internal server-side methods and read their return values.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

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


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

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

## Is CVE-2026-96672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96672 is a medium-severity code injection vulnerability in Frappe ERPNext, published on 23 Sep 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-96672 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-96672/ (Markdown: https://insights.sbomify.com/CVE-2026-96672/index.md)
```

## Sources

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

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