Frappe ERPNext 13.0.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in an
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 15.122.0 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 | 5.0 |
- Patch
- Available – fixed in 15.122.0, 16.50.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/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.122.0; erpnext to 16.50.0; frappe/erpnext to 16.50.0 or 15.122.0.
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
If you cannot patch yet, restrict Accounts User role permissions carefully and monitor for unusual reconciliation activities involving vouchers outside expected scopes.
Description
Frappe ERPNext versions 13.0.0 before 15.122.0 and 16.x before 16.50.0 have a missing authorization vulnerability in the Accounts module. This flaw allows authenticated users with the Accounts User role who can edit Bank Transactions to manipulate reconciliation states of vouchers outside their permission scope. The vulnerability arises because the system checks permissions only on the Bank Transaction, not on each voucher referenced in reconciliation requests.