CVE-2026-134430 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 12.0.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns the parsed content of private import-format files without checking permission on the requested records. Authenticated attackers, including portal users or users without roles, can send crafted requests naming records outside their permitted scope to read those private files.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The identified vulnerability represents a critical failure in access control mechanisms within the Frappe ERPNext framework, specifically affecting versions 12.0.0 prior to patch level 15.121.4 and version 16.x prior to release 16.36.0. This flaw resides within an endpoint associated with the Accounts module, which is designed to handle data imports and exports for financial records. The core technical deficiency lies in the server-side logic that processes requests for private import-format files. When a user submits a request specifying a particular record identifier, the system retrieves and returns the parsed content of the corresponding file without performing adequate authorization checks against the requesting user's permissions or role assignments. This absence of validation allows any authenticated entity to bypass intended security boundaries simply by manipulating the input parameters to reference records that are not part of their authorized scope.
From a technical perspective, this vulnerability is classified as an Insecure Direct Object Reference (IDOR), which corresponds to CWE-639 in the Common Weakness Enumeration standard. The root cause stems from the application's reliance on client-supplied identifiers or internal object references without cross-referencing them against the current session's access control list. By exploiting this logic error, an attacker can iterate through record IDs to enumerate and extract sensitive financial data stored within these private files. This includes potentially confidential invoices, payment details, vendor contracts, and other proprietary accounting information that should be restricted based on organizational hierarchy or departmental roles. The vulnerability effectively neutralizes the intended isolation between different user groups, turning a standard file retrieval function into a powerful data exfiltration tool.
The operational impact of this flaw is severe due to its potential for widespread data leakage within enterprise environments using ERPNext. Since authentication is required but role-based restrictions are ignored, even portal users with minimal privileges or accounts lacking specific administrative roles can access high-sensitivity financial records. This undermines the principle of least privilege and compromises the confidentiality integrity of the entire accounting system. Attackers could use this capability to conduct reconnaissance on an organization's financial health, identify valuable targets for further exploitation such as business email compromise schemes, or simply steal competitive intelligence contained within vendor agreements. The ease of exploitation means that automated scanning tools can rapidly harvest large volumes of sensitive data across multiple organizations running vulnerable versions.
Mitigation strategies must prioritize immediate patching to the latest stable releases where this authorization check has been implemented. Administrators should upgrade Frappe ERPNext to version 15.121.4 or later for the v12 branch, and version 16.36.0 or later for the v16 branch. Until patches are applied, organizations can implement compensating controls such as web application firewall rules that inspect request parameters for patterns indicative of IDOR attacks, although this is less effective than a code-level fix. Additionally, reviewing access logs for unusual spikes in file retrieval requests from low-privilege accounts may help detect ongoing exploitation attempts. Long-term remediation involves adopting secure coding practices that enforce explicit authorization checks at every data access point, ensuring that object references are validated against the user's permissions before any sensitive content is served. This aligns with MITRE ATT&CK technique T1078, Valid Accounts, as it demonstrates how legitimate credentials can be leveraged to bypass security controls when proper validation logic is absent.