CVE-2026-134432 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 15.0.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in a Stock module import endpoint that does not check whether the caller may create inserted records or download a named file. Authenticated attackers, including portal users or users with no roles, can send crafted import requests to read file contents and create Serial No and Batch records.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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 within the Stock module's import endpoint. This flaw is classified as an Insecure Direct Object Reference or, more accurately given the context of missing checks on creation capabilities, a Broken Access Control vulnerability aligned with CWE-284: Improper Access Control. The core technical issue lies in the server-side logic that processes incoming import requests without verifying whether the authenticated user possesses the necessary permissions to perform specific actions such as creating new records or downloading sensitive files. This oversight allows any authenticated entity, including portal users who typically have limited privileges and even unauthenticated visitors if session handling is compromised, to bypass intended security boundaries.
From a technical perspective, the vulnerability exploits the lack of authorization checks on two distinct operations facilitated by the import endpoint. First, attackers can craft specific requests that trigger the creation of Serial No and Batch records within the ERP system's database. These objects are fundamental to inventory management in Frappe ERPNext, tracking individual items and their production or purchase batches respectively. By injecting malicious data through this vector, an attacker can pollute the integrity of stock records, potentially leading to significant operational discrepancies, financial loss due to incorrect inventory counts, or further exploitation if these fields are used as inputs for other system functions. Second, the endpoint fails to validate whether a user is authorized to download named files associated with import operations. This allows unauthorized retrieval of file contents that may contain sensitive business data, customer information, or internal configuration details not intended for public or low-privilege access.
The operational impact of this vulnerability extends beyond simple data leakage or corruption. Because the flaw affects authenticated users including those with no specific roles, it effectively lowers the barrier to entry for attackers significantly. An adversary does not need high-level administrative privileges to exploit this issue; basic authentication is sufficient. This broadens the attack surface considerably, as any user account created in the system can be leveraged to compromise data integrity and confidentiality. The ability to create arbitrary Serial No and Batch records could also serve as a foothold for more complex attacks, such as supply chain poisoning or facilitating fraud by manipulating inventory levels artificially. Furthermore, unauthorized file downloads expose proprietary business logic or sensitive operational documents that are critical to the organization's competitive advantage and regulatory compliance.
This vulnerability maps directly to MITRE ATT&CK technique T1078: Valid Accounts, where attackers use legitimate credentials to gain access, combined with T1530: Data from Cloud Storage Object if file exfiltration is utilized for sensitive data retrieval. It also aligns with CWE-269: Improper Privilege Management due to the failure to enforce role-based restrictions on specific API endpoints. To mitigate this risk, organizations running affected versions of Frappe ERPNext must immediately upgrade to version 15.121.4 or later for the 15.x branch and version 16.36.0 or later for the 16.x branch. These updates include patches that enforce proper authorization checks on the import endpoint, ensuring that users can only perform actions consistent with their assigned roles and permissions. Additionally, administrators should review access logs to identify any potential exploitation attempts prior to patching and consider implementing strict input validation and role-based access control policies for all API endpoints handling sensitive data operations. Regular security audits focusing on authentication and authorization flows are recommended to prevent similar misconfigurations in the future.