CVE-2026-134419 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 10.0.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns Payment Terms Template rows 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 read Payment Terms Template data.
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 Accounts module of Frappe ERPNext versions prior to 15.122.0 and 16.x prior to 16.50.0. This flaw is classified as an Insecure Direct Object Reference, commonly referred to by its CWE identifier CWE-639. The core technical issue stems from the absence of proper authorization checks on a specific API endpoint responsible for retrieving Payment Terms Template rows. When a user requests data associated with these templates, the system fails to verify whether the authenticated caller possesses the necessary permissions or roles to access the specific record identified in the request parameters. This lack of server-side validation allows any authenticated entity to bypass intended security boundaries simply by manipulating the object reference included in their HTTP request.
The operational impact of this vulnerability is significant because it enables unauthorized data disclosure across a broad spectrum of user types within the ERPNext ecosystem. Unlike vulnerabilities that require high-level administrative privileges, this flaw can be exploited by portal users or even accounts with no assigned roles beyond basic authentication. An attacker who has successfully authenticated to the system can craft requests targeting Payment Terms Template records that are logically out-of-scope for their profile. By doing so, they can extract sensitive financial configuration data, including payment terms and associated template details, which may contain proprietary business logic or confidential contractual information intended only for authorized finance personnel or administrators.
This vulnerability aligns with the MITRE ATT&CK framework technique T1078, specifically under Valid Accounts, as it leverages legitimate authentication credentials to perform unauthorized actions. It also relates to T1530, Data from Local System, by allowing an attacker to exfiltrate data stored within the application database that they are not supposed to access. The exploitation does not require complex injection techniques or buffer overflows; instead, it relies on simple HTTP parameter manipulation where the attacker changes the identifier of the requested Payment Terms Template row in subsequent requests until they successfully retrieve restricted information.
To mitigate this vulnerability, organizations running affected versions must immediately upgrade Frappe ERPNext to version 15.122.0 or later for the v15 branch, or version 16.50.0 and later for the v16 branch. These updates include patches that enforce strict authorization checks on all data retrieval endpoints within the Accounts module. Until an upgrade is performed, administrators should consider implementing network-level controls such as Web Application Firewalls to monitor for anomalous patterns of access to Payment Terms Template resources by low-privilege accounts. Additionally, conducting a thorough review of custom scripts or integrations that interact with these API endpoints can help identify if any existing workflows are inadvertently exposing this data through alternative paths. Regular security audits focusing on object-level permission checks across all modules are recommended to prevent similar insecure direct object reference flaws in other parts of the application.