CVE-2026-134382 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in a Selling module endpoint that checks only document-type write permission, not permission on each Sales Order, when closing or reopening Sales Orders. Authenticated users restricted by User Permissions can send crafted requests naming another company's Sales Order to close or reopen it outside their restriction.
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 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 Selling module, specifically affecting the operations of closing or reopening Sales Orders. This flaw stems from an incorrect authorization logic where the system validates permissions at the document type level rather than enforcing granular checks on individual records. In enterprise resource planning systems like ERPNext, data isolation is paramount to ensure that users can only interact with information relevant to their specific organizational scope or role. The vulnerability arises because the endpoint responsible for these state transitions relies solely on verifying whether the authenticated user has write permission for the Sales Order document type in general, without subsequently checking if the specific instance of the Sales Order being targeted falls within the user's permitted boundaries defined by User Permissions.
This architectural oversight allows authenticated users who are restricted from viewing or modifying certain sales records to bypass these restrictions through crafted HTTP requests. By manipulating the request payload to specify a Sales Order identifier belonging to another company or entity, an attacker can successfully execute actions such as closing or reopening that order. This constitutes a classic case of Insecure Direct Object Reference combined with Broken Access Control, where the application fails to verify that the user is authorized to perform the requested action on the specific resource identified by the input parameter. The impact extends beyond simple data visibility; it allows for unauthorized state changes in business-critical documents, which can disrupt financial reporting, inventory management processes, and order fulfillment workflows.
From a threat modeling perspective, this vulnerability aligns with CWE-269 Improper Privilege Management and CWE-862 Missing Authorization, as the system fails to enforce proper access control policies on individual objects. It also maps to MITRE ATT&CK technique T1078 Valid Accounts, where an attacker uses legitimate credentials but exploits a logic flaw to perform actions outside their intended scope. The operational impact is significant because Sales Orders often trigger downstream processes such as shipping, invoicing, and revenue recognition. Unauthorized closure of an order might prevent necessary shipments or alter financial commitments, while unauthorized reopening could lead to duplicate processing or confusion in the supply chain. For organizations relying on ERPNext for multi-tenant operations or strict departmental data segregation, this flaw undermines the integrity of their business logic and compliance with internal governance standards.
Mitigation requires immediate application of the vendor-released patches updating Frappe ERPNext to version 15.121.4 or later, or version 16.36.0 and above, which corrects the authorization checks in the Selling module endpoints. In environments where patching is not immediately feasible, administrators should implement strict network-level access controls to limit exposure of these specific API endpoints to trusted internal networks only. Additionally, implementing Web Application Firewall rules that detect anomalous patterns in object reference parameters can provide a layer of defense against exploitation attempts. Long-term remediation strategies should include conducting code reviews focused on authorization logic for all document-centric operations and adopting automated security testing tools capable of identifying broken access control vulnerabilities during the development lifecycle to prevent similar issues from being introduced into future releases.