CVE-2026-134428 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 13.0.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in a Stock module endpoint that returns Item master records without checking whether the caller may read the requested records. Authenticated attackers, including portal users or users with no assigned roles, can send crafted requests naming out-of-scope records to retrieve complete item data including costing and purchase rates.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Frappe ERPNext versions prior to 13.x before 15.121.4 and 16.x before 16.36.0 represents a critical failure in access control mechanisms within the Stock module. This flaw specifically affects an endpoint responsible for retrieving Item master records, which serves as a central repository of product information used across various business operations including inventory management, procurement, and sales. The core technical deficiency lies in the absence of proper authorization checks when processing requests to fetch these records. Instead of validating whether the authenticated user possesses the necessary permissions or roles associated with specific data scopes, the system blindly returns the requested Item master details based solely on the identifier provided in the request payload. This design oversight allows any authenticated entity interacting with this endpoint to bypass intended security boundaries and access sensitive information that should be restricted by role-based access control policies.
From a technical perspective, this vulnerability is classified as an Insecure Direct Object Reference (IDOR), which aligns with CWE-639 in the Common Weakness Enumeration standard. The attacker exploits the predictable nature of object identifiers or simply iterates through valid record IDs to enumerate data that falls outside their authorized scope. Because the server does not verify if the requesting user has permission to view the specific Item ID being requested, it results in a complete breakdown of confidentiality controls. This is particularly dangerous in an Enterprise Resource Planning system where item master records often contain proprietary business intelligence such as cost prices, supplier purchase rates, and margin calculations. These data points are typically considered sensitive financial information that should only be accessible to authorized personnel like procurement managers or finance teams, not general users or portal visitors who interact with the system for basic transactions.
The operational impact of this vulnerability is significant due to the potential for unauthorized disclosure of confidential business data. Authenticated attackers, including those with minimal privileges such as standard portal users or accounts lacking specific roles, can craft requests to retrieve complete item profiles. This includes sensitive financial metrics like costing details and purchase rates which are critical for competitive analysis if leaked. An adversary could aggregate this information across multiple items to gain insights into the organization's supply chain costs, profit margins, and vendor relationships. Furthermore, because ERPNext is often deployed in multi-tenant environments or used by organizations with complex user hierarchies, a single compromised account can lead to widespread data exposure without requiring privilege escalation attacks. This undermines trust in the system’s security model and may violate regulatory compliance requirements regarding data protection and confidentiality of financial records.
Mitigation strategies must focus on implementing robust authorization checks at both the application logic level and the framework configuration layer. Developers should ensure that every endpoint performing read operations validates the current user's permissions against the specific resource being accessed, rather than relying solely on authentication tokens or session validity. This involves integrating role-based access control (RBAC) middleware into the Stock module’s API handlers to verify that the requesting entity has explicit permission for each Item ID requested. Additionally, implementing object-level security checks where the database query includes a condition verifying user ownership or group membership can prevent unauthorized enumeration. For administrators using affected versions, immediate upgrading to version 15.121.4 or later for the v13 branch and version 16.36.0 or later for the v16 branch is essential as these releases contain patches addressing this authorization flaw. Until upgrades are applied, network-level controls such as Web Application Firewalls (WAF) can be configured to detect anomalous patterns of ID enumeration requests targeting item master endpoints, providing a temporary layer of defense against exploitation attempts aligned with ATT&CK technique T1078 which involves valid accounts being used for unauthorized access.