CVE-2026-134408 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 16.0.1 before 16.50.0 contains a missing authorization vulnerability in a Stock dashboard chart endpoint that returns site-wide stock value when the caller has no permitted warehouse. Authenticated users with common operational roles can send crafted requests naming records outside their scope to read stock value data beyond their permissions.
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 identified vulnerability represents a critical failure in access control mechanisms within Frappe ERPNext versions prior to 16.50.0, specifically affecting the Stock dashboard chart endpoint. This flaw allows authenticated users with standard operational roles to bypass intended permission boundaries and retrieve sensitive inventory data that they are not authorized to view. The core issue lies in the server-side logic responsible for processing requests related to stock value calculations. When a user initiates a request to fetch site-wide stock values, the application fails to adequately verify whether the requesting user possesses valid permissions for all warehouses or locations referenced in the query context. Instead of enforcing strict role-based access control checks against each specific warehouse entity involved in the calculation, the system relies on insufficient validation logic that permits the aggregation and return of data across the entire site if certain conditions are met, effectively ignoring the granular permission sets assigned to individual users.
From a technical perspective, this vulnerability is classified under CWE-285, which describes Improper Authorization, as well as CWE-639, Injection into Command or Script that Invokes an Indirectly Referenced Command with Unintended Right Constraints, depending on the specific implementation details of how the warehouse scope is parsed. The attacker exploits this by crafting HTTP requests that target the stock dashboard endpoint while omitting explicit warehouse identifiers or manipulating parameters to trigger a site-wide aggregation query. Because the authentication layer successfully validates the user's session and role, but the authorization layer fails to restrict data access based on those roles, the system returns comprehensive financial inventory data. This includes total stock values across all warehouses, regardless of whether the authenticated user has visibility into any specific warehouse location. The vulnerability is particularly dangerous because it does not require administrative privileges; common operational staff with minimal permissions can leverage this flaw to gain unauthorized insight into company-wide asset valuations and inventory levels.
The operational impact of this information disclosure is significant for organizations relying on ERPNext for financial oversight and supply chain management. Stock value data constitutes sensitive business intelligence, reflecting current asset liquidity, potential losses due to obsolescence or damage, and overall financial health related to inventory holdings. Unauthorized access to site-wide stock values can lead to competitive disadvantage if such data leaks to external parties, internal fraud where employees might manipulate records based on hidden knowledge of total assets, or strategic missteps by management who rely on accurate but potentially compromised reporting structures. Furthermore, the ability to read data outside one's scope undermines the principle of least privilege, a cornerstone of secure system design, and can facilitate further attacks such as social engineering or targeted exploitation if combined with other vulnerabilities in the ERP suite.
To mitigate this vulnerability, organizations must immediately upgrade their Frappe ERPNext instances to version 16.50.0 or later, where these access control checks have been corrected. In environments where immediate patching is not feasible due to operational constraints, temporary mitigations should focus on network-level restrictions and enhanced monitoring. Implementing strict firewall rules to limit access to the dashboard endpoints only from trusted internal IP ranges can reduce exposure. Additionally, deploying Web Application Firewalls with custom rules to detect anomalous request patterns targeting stock value APIs may help block exploitation attempts. It is also advisable to review user roles and permissions within ERPNext to ensure that no single role inadvertently grants broad data visibility without corresponding warehouse-specific restrictions. Regular security audits focusing on authorization logic in financial modules are recommended to prevent similar access control failures in other parts of the application ecosystem aligned with MITRE ATT&CK techniques related to Collection and Exfiltration over Application Layer Communication.