CVE-2026-13227 json
ERPNext v16.25.0 - Improper authorization in Prospect opportunities API
published 2026-08-04 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-52924
- cvss
- 7.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- fluidattacks.com https://fluidattacks.com/es/advisories/kraviz referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- Frappe ERPNext
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
github.com
/frappe/erpnext/releases?page=2#release-v15.115.0
patch
-
github.com
/frappe/erpnext/releases?page=2#release-v16.26.0
patch
-
fluidattacks.com
/es/advisories/kraviz
third-party-advisory, exploit
-
github.com
/frappe/erpnext/security/advisories/GHSA-g8r3-82j6-wp48
vendor-advisory
-
github.com
/frappe/erpnext
product
Sources
- CVE List CVE-2026-13227
- NVD CVE-2026-13227
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.