CVE-2026-134394 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 14.44.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in the Accounts module's payment unreconciliation endpoint, which does not check the caller's permission on the vouchers it unreconciles. Authenticated users with the Accounts User role can send crafted Unreconcile Payment requests naming vouchers from other companies or outside their User Permissions to remove their reconciliation.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in Frappe ERPNext versions prior to 15.122.0 and 16.x before 16.50.0 represents a critical failure in access control mechanisms within the Accounts module. Specifically, the flaw resides in the payment unreconciliation endpoint, which is designed to reverse previously recorded financial reconciliations. In a robust enterprise resource planning system, such operations must be strictly gated by authorization checks that verify whether the initiating user has explicit permission to modify or interact with specific financial records. However, this implementation fails to validate the caller's permissions against the target vouchers before processing the unreconciliation request. This oversight allows authenticated users possessing the Accounts User role to bypass intended security boundaries and manipulate financial data belonging to other entities within the system.

From a technical perspective, the core issue is an insecure direct object reference combined with missing function level access control. When a user submits a crafted Unreconcile Payment request, the backend logic accepts the voucher identifier provided in the payload without cross-referencing it against the User Permissions table or verifying organizational boundaries. In ERPNext, data isolation is typically enforced through company-specific permissions and role-based access controls that restrict users to viewing and editing only those records associated with their assigned companies or specific user permission rules. By neglecting these checks during the unreconciliation process, the application effectively treats all voucher IDs as accessible resources for any authenticated Accounts User, regardless of whether they own the data or have been granted explicit rights to alter it.

The operational impact of this vulnerability is severe due to the financial nature of the affected module. An attacker with valid credentials and the Accounts User role can arbitrarily remove reconciliations from vouchers belonging to other companies within the same ERPNext instance. This action disrupts the integrity of financial records, potentially leading to inaccurate reporting, audit trail corruption, and confusion in accounting workflows. Furthermore, by unreconciling payments that were previously matched against invoices or bank statements, an attacker could create discrepancies that obscure fraudulent activities or facilitate further manipulation of the ledger. The ability to alter data outside one's authorized scope undermines trust in the system’s reliability and compliance with financial regulations such as SOX or GDPR, which require strict integrity controls over sensitive business information.

This vulnerability aligns closely with CWE-269, Improper Privilege Management, specifically where a user can perform actions beyond their assigned privileges. It also maps to MITRE ATT&CK technique T1078, Valid Accounts, as the exploitation relies on legitimate credentials, and potentially T1534, Internal Spearphishing if used in conjunction with social engineering, though here it is primarily an internal privilege escalation or lateral movement risk within the application logic. The lack of authorization checks constitutes a classic broken access control scenario where the system assumes that because a user is authenticated and has a general role like Accounts User, they should have unrestricted write access to all financial documents associated with that module type.

To mitigate this vulnerability, organizations must upgrade Frappe ERPNext immediately to version 15.122.0 or later for the v15 branch, or version 16.50.0 and above for the v16 branch, where these authorization checks have been implemented. Until an upgrade is feasible, administrators should enforce strict role-based access controls by limiting the Accounts User role to only those individuals who absolutely require it, thereby reducing the attack surface. Additionally, implementing network-level segmentation can help isolate ERPNext instances from untrusted networks, although this does not mitigate insider threats or compromised credentials within trusted zones. Regular audits of user permissions and monitoring for unusual patterns in financial data modifications are recommended as supplementary defensive measures to detect potential exploitation attempts early.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!