# CVE-2026-13227: ERPNext v16.25.0 - Improper authorization in Prospect opportunities API

> Attackers can access Prospect opportunities data without proper authorization due to insufficient access control in the API.

- **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:** 4 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-g8r3-82j6-wp48

## What is CVE-2026-13227?

CVE-2026-13227 is a high-severity missing authorization vulnerability in Frappe ERPNext, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Improper Authorization vulnerability exists in ERPNext version <v16.25.0 and <15.115.0  due to insufficient access control in the whitelisted API method erpnext.crm.doctype.prospect.prospect.get_opportunities.

This issue affects ERPNext: before 15.115.0, before 16.26.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-13227 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13227 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13227 is a high-severity missing authorization vulnerability in Frappe ERPNext, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13227 exists.

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-13227/ (Markdown: https://insights.sbomify.com/CVE-2026-13227/index.md)
```

## Sources

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

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