CVE-2026-134395 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 amounts and bank accounts without checking whether the caller may read the requested records. Authenticated users with a common operational role can send crafted requests naming out-of-scope records to read Bank Transaction data of other companies.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The identified security flaw resides within the Accounts module of Frappe ERPNext, 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 vulnerability is classified as a missing authorization issue, which fundamentally represents an access control failure where the application fails to enforce proper restrictions on authenticated users regarding specific resources. In this context, the vulnerable endpoint is designed to return Bank Transaction amounts and associated bank account details for financial reporting or operational purposes. However, the implementation lacks critical validation logic that verifies whether the requesting user possesses the necessary permissions to view the data corresponding to the requested record identifiers. This oversight allows any authenticated user with a standard operational role to bypass intended security boundaries by manipulating request parameters to target records belonging to other companies within the same multi-tenant instance or system environment.
From a technical perspective, this vulnerability aligns directly with CWE-284, which describes Improper Access Control, and more specifically CWE-639 regarding Authorization Bypass Through User-Controlled Key in web applications. The core mechanism of exploitation involves an authenticated attacker sending crafted HTTP requests to the affected endpoint while specifying identifiers for Bank Transaction records that are not associated with their own company or organizational unit. Because the server-side logic does not cross-reference these requested record IDs against the user's assigned permissions and tenant context, it proceeds to serialize and return sensitive financial data regardless of ownership. This behavior violates the principle of least privilege and fails to implement proper object-level access controls, which are essential for maintaining data isolation in multi-tenant enterprise resource planning systems where distinct companies share a single software instance but must maintain strict separation of their proprietary financial information.
The operational impact of this vulnerability is significant due to the sensitivity of the exposed data. Bank Transaction amounts and bank account details constitute highly confidential financial information that, if disclosed, can lead to severe business consequences including fraud, competitive disadvantage, or regulatory non-compliance with standards such as PCI DSS or SOX depending on the industry sector. An attacker leveraging this flaw could systematically enumerate valid record identifiers through brute-force techniques or by exploiting other informational disclosures within the application to map out financial structures of competing entities or internal departments they are not authorized to access. This capability effectively neutralizes the security model's ability to protect sensitive corporate data from insider threats or compromised accounts with low-level privileges, thereby exposing the organization to potential financial loss and reputational damage resulting from unauthorized data exfiltration.
In terms of threat modeling, this vulnerability facilitates actions consistent with ATT&CK technique T1530, Data from Cloud Storage Object Discovery, as it involves enumerating accessible objects within a cloud-hosted or web-based application environment. It also relates to T1078, Valid Accounts, since the exploitation requires prior authentication but exploits insufficient authorization checks rather than credential theft. To mitigate this risk, organizations running affected versions of Frappe ERPNext must immediately upgrade to version 15.122.0 or later for the v13 branch and version 16.50.0 or later for the v16 branch where these access control validations have been implemented by the vendor. Additionally, administrators should review their role-based permission settings to ensure that operational roles are granted only the minimum necessary privileges required for daily tasks, thereby reducing the blast radius in case of future vulnerabilities. Implementing strict input validation and enforcing server-side ownership checks on all API endpoints handling sensitive financial data is critical to preventing similar authorization bypasses across the application ecosystem.