CVE-2026-134405 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 returns Bank Transaction metadata of other companies without checking whether the caller may read the requested records. Authenticated attackers, including portal users or users with no assigned roles, can send crafted requests naming out-of-scope records to retrieve that metadata.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The identified vulnerability represents a critical failure in access control mechanisms within the Frappe ERPNext framework, specifically affecting versions 13.0.0 prior to patch level 15.122.0 and version 16.x prior to patch level 16.50.0. This flaw resides in an endpoint dedicated to retrieving Bank Transaction metadata within the Accounts module. The core technical deficiency is a missing authorization check, which means that while the system verifies that a user is authenticated, it fails to validate whether that specific user possesses the necessary permissions to access the requested resource. Consequently, any request made to this endpoint returns sensitive financial data associated with other companies or entities within the multi-tenant environment, regardless of the caller's role or assigned privileges.
From an operational perspective, this vulnerability allows for significant information disclosure and potential business logic abuse. Authenticated attackers, including those utilizing portal users who typically have restricted access levels, as well as users with no specific roles assigned at all, can exploit this flaw by crafting HTTP requests that specify identifiers belonging to out-of-scope records. By manipulating the input parameters of these requests, an attacker can bypass standard isolation boundaries and retrieve metadata for bank transactions they are not authorized to view. This exposure compromises the confidentiality of financial data across different organizational units or tenants sharing the same ERPNext instance, potentially revealing sensitive details such as transaction amounts, dates, counterparties, and internal reference numbers that should remain strictly isolated.
The security implications align closely with CWE-284, which describes Improper Access Control, specifically highlighting failures in authorization checks where access to resources is not properly restricted based on user identity or role. Furthermore, this vulnerability facilitates data exfiltration techniques categorized under the MITRE ATT&CK framework as Collection via Unsecured API (T1567) and potentially contributes to Reconnaissance activities by allowing attackers to map out financial structures of other entities within the system. The ability for users with minimal privileges to access high-sensitivity data underscores a severe gap in the principle of least privilege, which is fundamental to secure enterprise resource planning systems.
To mitigate this risk, organizations running affected versions must immediately apply the recommended patches by upgrading Frappe ERPNext to version 15.122.0 or later for the v13 branch, and version 16.50.0 or later for the v16 branch. These updates include necessary code changes that enforce proper authorization checks on the Bank Transaction metadata endpoint. In addition to patching, administrators should review their access control policies to ensure that role-based permissions are strictly enforced across all modules, particularly those handling financial data. Implementing robust input validation and ensuring that every API endpoint performs a secondary verification of user privileges against the specific resource being accessed will further harden the system against similar authorization bypass attempts in the future.