CVE-2026-134386 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 15.111.0 before 15.121.4 and 16.22.0 before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns item rows of a caller-named inter-company invoice or order and accepts a caller-supplied document type without checking read permission. Authenticated attackers, including portal users or users with no roles, can send crafted requests naming another company's document to read Sales Invoice, Purchase Invoice and order items.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Frappe ERPNext versions prior to 15.121.4 for the v15 branch and before 16.36.0 for the v16 branch represents a critical failure in access control mechanisms within the Accounts module. This flaw specifically affects an endpoint designed to retrieve item rows associated with inter-company invoices or orders. The core technical deficiency lies in the server-side logic, which accepts a caller-supplied document type parameter and uses it to fetch data based on a provided identifier without performing any verification of the requesting user's permissions against that specific resource. This absence of authorization checks allows for unauthorized access to sensitive financial records, fundamentally breaking the principle of least privilege required for enterprise resource planning systems handling multi-tenant or inter-company transactions.
From an operational perspective, this missing authorization vulnerability enables authenticated attackers to exfiltrate data belonging to other companies within the same ERPNext instance. The impact is severe because it affects Sales Invoices and Purchase Invoices, which contain highly sensitive commercial information including pricing, quantities, customer details, and supplier contracts. Attackers do not need elevated privileges or specific roles; even portal users with minimal access rights or unauthenticated accounts that have managed to gain initial entry can exploit this flaw. By crafting requests that specify the document type of another company's invoice or order, an attacker can retrieve detailed item-level data, leading to a significant confidentiality breach and potential competitive disadvantage for affected organizations.
This vulnerability aligns directly with CWE-284, which describes Improper Access Control, as well as CWE-639 regarding Authorization Bypass Through User-Controlled Key. The attack vector is consistent with MITRE ATT&CK technique T1078, specifically the Valid Accounts subcategory, where attackers leverage legitimate credentials to access resources they are not authorized to view. In multi-tenant environments or organizations using ERPNext for complex inter-company operations, this flaw undermines data isolation guarantees that are essential for maintaining trust and compliance with regulations such as GDPR or SOX.
Mitigation strategies must prioritize immediate patching of the Frappe framework and ERPNext application to versions 15.121.4 or later for v15 users, and 16.36.0 or later for v16 users. These updates include the necessary code changes to enforce proper authorization checks before returning data from the affected endpoint. In addition to patching, organizations should implement strict input validation on all API endpoints that accept document identifiers, ensuring that every request is validated against the current user's permission set and tenant context. Security teams should also audit existing access control lists and review custom scripts or integrations that interact with the Accounts module to ensure no similar bypasses exist in other parts of the application. Regular penetration testing focusing on horizontal privilege escalation can help identify such flaws before they are exploited in production environments.