CVE-2026-134436 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 15.8.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an endpoint shared across modules that returns transaction child table rows without checking permissions on the child table or parent document. Authenticated attackers, including portal users or users without roles, can supply document types and filter conditions to read business document line details and probe record values.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The identified vulnerability in Frappe ERPNext versions prior to 15.121.4 for the 15.x branch and before 16.36.0 for the 16.x branch represents a critical failure in access control mechanisms, specifically categorized under CWE-862 Missing Authorization. This flaw resides within an API endpoint that is shared across multiple modules of the enterprise resource planning system. The core technical deficiency lies in the server-side logic which retrieves transaction child table rows without performing any validation checks against permissions associated with either the specific child table or its parent document. In a properly secured application, every data retrieval operation must verify that the requesting user has explicit rights to view the requested resources based on their role and assigned privileges. However, this implementation bypasses those essential security gates, allowing for unrestricted access to sensitive transactional data structures.
The operational impact of this vulnerability is severe due to its broad applicability across different modules within the ERPNext ecosystem. Because the endpoint does not distinguish between high-level administrative functions and basic user operations, it exposes a wide array of business-critical information. Authenticated attackers, including portal users who may have minimal or no specific roles assigned, can exploit this flaw by supplying arbitrary document types along with filter conditions to query the database directly. This capability enables them to read detailed line items from financial transactions, inventory records, and other operational data that should be restricted based on organizational hierarchy and user permissions. The ability to probe record values means attackers can not only view existing data but also infer structural details about how information is stored, potentially facilitating further attacks such as SQL injection or targeted social engineering campaigns using harvested sensitive business intelligence.
From a threat modeling perspective, this vulnerability aligns with MITRE ATT&CK technique T1078 Valid Accounts, where adversaries leverage legitimate credentials to access resources they are not authorized to view. It also relates to CWE-200 Information Exposure, as the system inadvertently discloses internal data structures and business logic through its API responses. The lack of authorization checks on child tables is particularly dangerous because these tables often contain granular details such as pricing, quantities, customer identities, and supplier information that are central to an organization's competitive advantage and regulatory compliance status. By exploiting this flaw, malicious actors can conduct extensive data exfiltration without triggering typical intrusion detection systems that monitor for unauthorized login attempts or privilege escalation events, since the attacker is using valid credentials throughout the process.
To mitigate this vulnerability, organizations running affected versions of Frappe ERPNext must immediately upgrade to version 15.121.4 or later if operating on the 15.x branch, or version 16.36.0 and later for those on the 16.x branch. These updates contain patches that enforce proper authorization checks at both the parent document level and the child table level before returning any data through the shared endpoint. In addition to upgrading, administrators should review their API gateway configurations to ensure rate limiting is applied to these endpoints to prevent automated probing attacks while patching efforts are underway. It is also advisable to audit existing user roles and permissions within the ERPNext instance to minimize the blast radius of this vulnerability by ensuring that even if an attacker gains access via a low-privilege account, their ability to query sensitive data types is restricted as much as possible through role-based access control policies. Regular security assessments focusing on API endpoints are recommended to detect similar authorization flaws in other parts of the application architecture.