Frappe ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in the
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 15.121.4 when convenient.
Data as of 21 Nov 2026, 19:43 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.3 |
- Patch
- Available – fixed in 15.121.4, 16.36.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade erpnext to 15.121.4; erpnext to 16.36.0; frappe/erpnext to 16.36.0 or 15.121.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| frappeerpnext | Affected
| Fixed in
|
| frappeerpnext | Affected
| Fixed in
|
GitHubfrappe/erpnextpkg:github/frappe/erpnextOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Frappe ERPNext versions 15.121.4 and later for the 5.0.0 branch and 16.36.0 and later for the 16.x branch. Users should upgrade to these versions to remediate the incorrect authorization vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary workarounds.
Description
Frappe ERPNext versions 5.0.0 before 15.121.4 and 16.x before 16.36.0 have an authorization vulnerability in the Buying module. The endpoint responsible for closing and reopening Purchase Orders only verifies document-type write permissions, ignoring per-document User Permissions. This allows authenticated users with Purchase Order write access to alter the status of Purchase Orders belonging to other companies by sending crafted requests.