Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108374 Overview
CVE-2026-108374 is a missing authorization vulnerability [CWE-862] in ERPNext, the open source Enterprise Resource Planning (ERP) tool built on the Frappe framework. Several state-changing whitelisted methods omit required permission checks. A low-privileged authenticated user can invoke these endpoints to modify records beyond their assigned role, bypassing write, submit, cancel, document, and role checks. The issue affects ERPNext versions prior to 15.121.0 and 16.34.0, and is patched in those releases.
Critical Impact
Authenticated low-privileged users can trigger state changes on ledger merges, payment orders, and other objects they are not authorized to modify.
Affected Products
- ERPNext versions prior to 15.121.0 (15.x branch)
- ERPNext versions prior to 16.34.0 (16.x branch)
- Deployments relying on role-based permissions for whitelisted RPC methods
Discovery Timeline
- 2026-10-16 - CVE-2026-108374 published to the National Vulnerability Database (NVD)
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-108374
Vulnerability Analysis
ERPNext exposes server-side Python functions to authenticated clients via the @frappe.whitelist() decorator. These functions are reachable through the Frappe RPC endpoint and are intended to enforce document-level permissions before performing state changes. In the affected versions, several whitelisted methods omit a check_permission() call before mutating documents such as Ledger Merge and Payment Order. Any authenticated user with network access to the ERPNext instance can call these methods and cause side effects such as starting a ledger merge or generating payment journal entries. The missing checks remove the authorization layer that normally separates read-only or limited roles from accountants and administrators.
Root Cause
The root cause is a missing authorization check [CWE-862] in multiple @frappe.whitelist()-decorated functions. The functions loaded the target document via frappe.get_doc(...) and immediately invoked state-changing operations without calling check_permission() or has_permission() first. ERPNext's documented security model requires each whitelisted mutator to validate write, submit, or cancel rights for the invoking user, which these endpoints failed to do.
Attack Vector
Exploitation requires only valid session credentials for the target ERPNext instance. The attacker sends an authenticated HTTP request to the Frappe method endpoint (for example, /api/method/erpnext.accounts.doctype.ledger_merge.ledger_merge.form_start_merge) with the identifier of a target document. The server processes the state change under the attacker's session without validating role or document-level permissions, resulting in unauthorized modification of financial records.
# Patch excerpt - erpnext/accounts/doctype/ledger_merge/ledger_merge.py
@frappe.whitelist()
def form_start_merge(docname):
- return frappe.get_doc("Ledger Merge", docname).start_merge()
+ lm_doc = frappe.get_doc("Ledger Merge", docname)
+ lm_doc.check_permission("write")
+ return lm_doc.start_merge()
# Patch excerpt - erpnext/accounts/doctype/payment_order/payment_order.py
@frappe.whitelist()
def make_payment_records(name, supplier, mode_of_payment=None):
doc = frappe.get_doc("Payment Order", name)
+ doc.check_permission()
make_journal_entry(doc, supplier, mode_of_payment)
Source: GitHub ERPNext Commit a20fc4f
Detection Methods for CVE-2026-108374
Indicators of Compromise
- Requests to /api/method/erpnext.accounts.doctype.ledger_merge.ledger_merge.form_start_merge originating from user accounts that do not have the Accounts Manager or System Manager role.
- Requests to /api/method/erpnext.accounts.doctype.payment_order.payment_order.make_payment_records from accounts with no documented need to generate journal entries.
- Unexpected Journal Entry or Ledger Merge records created or modified by low-privileged users in the Frappe activity log.
Detection Strategies
- Review the Frappe Activity Log and Access Log doctypes for state changes performed by users whose roles should not permit write, submit, or cancel on the target doctype.
- Correlate web server access logs for POST requests to /api/method/erpnext.accounts.* endpoints with the authenticated user's assigned roles.
- Alert on anomalous spikes of calls to whitelisted methods tied to accounting doctypes from a single session.
Monitoring Recommendations
- Forward ERPNext application logs, Frappe audit logs, and reverse-proxy access logs to a central analytics platform for retention and correlation.
- Baseline normal usage of accounting-related whitelisted endpoints per role and alert on deviations.
- Enable Frappe's document version history on financial doctypes so unauthorized state changes can be reconstructed.
How to Mitigate CVE-2026-108374
Immediate Actions Required
- Upgrade ERPNext to 15.121.0 on the 15.x branch or 16.34.0 on the 16.x branch without delay.
- Audit user roles and remove unnecessary access to ERPNext accounts for any account that does not require it.
- Review recent Ledger Merge, Payment Order, and Journal Entry activity for unauthorized changes performed before patching.
Patch Information
The Frappe team fixed the issue by adding check_permission() calls to the affected whitelisted methods. The fix is tracked in commits 547d82d, 86e9480, and a20fc4f, and released in ERPNext v15.121.0 and ERPNext v16.34.0. Additional details are documented in GitHub Security Advisory GHSA-5wpj-6rvp-9ff7.
Workarounds
- Restrict network access to ERPNext administrative endpoints to trusted networks or VPN users until the patch is applied.
- Reduce the number of accounts holding login access to ERPNext and enforce multi-factor authentication for all remaining accounts.
- Temporarily disable integrations or self-registration flows that provision low-privileged accounts on the ERPNext instance.
# Upgrade ERPNext using the bench CLI
bench switch-to-branch version-15 erpnext --upgrade
bench update --reset
bench --site <site-name> migrate
# Verify the installed version is patched (>= 15.121.0 or >= 16.34.0)
bench version erpnext
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

