CVE-2026-134416 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 15.55.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns a company's Chart of Accounts without checking whether the caller may read the requested records. Authenticated users, including portal users or users with no assigned roles, can send crafted requests naming out-of-scope records to read any company's Chart of Accounts.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Frappe ERPNext versions prior to 15.121.4 and 16.x prior to 16.36.0 represents a critical failure in access control mechanisms within the application’s Accounts module. This flaw specifically affects an API endpoint responsible for retrieving a company's Chart of Accounts, which is a foundational data structure defining financial accounts such as assets, liabilities, equity, income, and expenses. The core technical deficiency lies in the absence of proper authorization checks when processing requests to this endpoint. Instead of validating whether the authenticated user possesses the necessary permissions or belongs to an authorized role for accessing specific company records, the system blindly returns the requested data based solely on the identifier provided in the request payload. This design oversight allows any authenticated individual to bypass intended security boundaries by manipulating input parameters to target resources outside their designated scope.
From a technical perspective, this vulnerability is classified under CWE-284, which denotes Improper Access Control. The exploitation vector relies on Insecure Direct Object References (IDOR), where the application uses user-supplied input directly to access objects without verifying that the requester has permission to do so. Because the endpoint does not enforce row-level or object-level security checks against the current session's privileges, an attacker can simply alter the company identifier in their HTTP request to query data belonging to other organizations within the same ERPNext instance. This is particularly dangerous because it affects even portal users and accounts with no assigned roles beyond basic authentication, highlighting a severe lapse in implementing the principle of least privilege. The vulnerability enables unauthorized disclosure of sensitive financial configurations that are typically restricted to administrators or specific accounting personnel.
The operational impact of this flaw extends beyond mere data leakage; it compromises the integrity and confidentiality of an organization's entire financial framework. An attacker with access to any user account, regardless of its assigned role, can extract detailed charts of accounts from multiple companies if they exist within the same instance. This information is highly sensitive as it reveals the structural layout of a company’s finances, including specific cost centers, profit and loss categories, and balance sheet structures. Such data could be leveraged by malicious actors to facilitate further attacks, such as crafting more convincing phishing campaigns tailored to an organization's financial processes or planning internal fraud schemes that exploit knowledge of account hierarchies. Furthermore, the exposure undermines trust in the ERP system’s ability to isolate multi-tenant environments effectively, potentially violating regulatory compliance requirements regarding data segregation and confidentiality.
Mitigation strategies must focus on immediate patching and enhanced access control implementation. The primary remediation is to upgrade Frappe ERPNext to version 15.121.4 or later for the v15 branch, or version 16.36.0 or later for the v16 branch, where these authorization checks have been corrected. In environments where immediate patching is not feasible due to operational constraints, temporary mitigations should include restricting access to the affected API endpoint via web application firewalls by validating session tokens against expected role permissions before allowing requests through. Additionally, developers and administrators should audit other endpoints within the Accounts module for similar patterns of missing authorization checks. Implementing robust server-side validation that cross-references user roles with resource ownership is essential to prevent IDOR attacks across all modules. Regular security audits and penetration testing focused on access control logic are recommended to ensure ongoing resilience against such vulnerabilities, aligning with ATT&CK techniques related to Collection via API Abuse and Unauthorized Access to Resources.