CVE-2026-134396 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 13.0.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in an Accounts module endpoint that reconciles Bank Transactions against caller-named vouchers, checking permission only on the Bank Transaction and not on each voucher. Authenticated users with the Accounts User role who can edit a Bank Transaction can send crafted requests naming vouchers outside their permitted scope to change the reconciliation state of vouchers belonging to other companies or outside their User Permissions.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Frappe ERPNext versions 13.0.0 prior to 15.122.0 and version 16.x prior to 16.50.0 represents a critical failure in access control logic within the Accounts module, specifically affecting the bank transaction reconciliation endpoint. This flaw allows authenticated users with the Accounts User role to manipulate financial records beyond their authorized scope by exploiting insufficient authorization checks on associated data objects. The core technical issue lies in the application's handling of voucher references during the reconciliation process. When a user initiates a request to reconcile a Bank Transaction, the system verifies that the user has permission to edit or view that specific Bank Transaction record. However, it fails to perform equivalent access control validations for each individual voucher referenced within that transaction. This architectural oversight creates a direct path for privilege escalation and data integrity compromise, as the application trusts the client-side input regarding which vouchers are being reconciled without validating whether the requesting user has explicit permissions to modify those specific voucher records.
From an operational perspective, this vulnerability enables attackers with relatively low-level privileges to alter the financial state of documents belonging to other companies or entities outside their designated User Permissions. In a multi-tenant ERP environment, where data isolation is paramount for compliance and security, this lack of cross-object authorization check allows an attacker to mark vouchers as reconciled that they should not have access to modify. This can lead to significant discrepancies in financial reporting, potential fraud concealment, or the disruption of audit trails. The impact extends beyond simple unauthorized modification; it undermines the fundamental trust model of the ERP system by allowing users to bypass granular permission settings defined at the voucher level. An attacker could potentially mask fraudulent transactions or alter the status of critical financial instruments without triggering standard security alerts associated with direct access violations, as the initial entry point appears legitimate under the existing authorization rules for the Bank Transaction itself.
This vulnerability aligns closely with CWE-269, which describes Improper Privilege Management, specifically highlighting cases where an actor is granted privileges that are not appropriate for their role or intended scope of action. Furthermore, it maps to MITRE ATT&CK technique T1078, Valid Accounts, as the exploitation relies on legitimate authentication credentials but abuses them through flawed authorization logic rather than credential theft. The specific mechanism also reflects aspects of CWE-926, Improper Export of Data with Incorrect Security Attributes, insofar as data intended for restricted access is exposed to modification by unauthorized actors due to misconfigured security attributes during processing. Understanding these mappings helps organizations contextualize the severity and nature of the flaw within broader cybersecurity frameworks, emphasizing that authentication alone is insufficient without rigorous authorization checks on all related resources involved in a transactional operation.
To mitigate this vulnerability, administrators must upgrade Frappe ERPNext immediately to version 15.122.0 or later for the v13 branch, and version 16.50.0 or later for the v16 branch, as these releases contain patches that enforce proper authorization checks on all vouchers involved in bank reconciliation processes. Until an upgrade is feasible, organizations should implement strict network-level access controls to limit exposure of the ERPNext instance to only trusted IP addresses and ensure that multi-factor authentication is enabled to reduce the risk of credential compromise leading to exploitation. Additionally, security teams should review existing User Permissions within the system to minimize the number of users with Accounts User roles, applying the principle of least privilege strictly. Regular auditing of bank transaction reconciliation logs can help detect anomalous patterns where vouchers from unrelated companies or unauthorized scopes are being modified by a single user account, providing an early warning mechanism for potential exploitation attempts while technical remediation is pending.