CVE-2026-134418 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 4.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 the taxes and charges of documents without checking record permissions. Authenticated users, including portal users or users with no roles, can request arbitrary document types and records to read tax rows beyond their permitted scope.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The identified security flaw resides within the Frappe ERPNext framework, specifically affecting versions prior to 15.122.0 in the legacy branch and before version 16.50.0 in the current release line. This vulnerability is classified as a missing authorization issue that impacts an endpoint responsible for retrieving tax and charge details associated with various business documents within the Accounts module. The core technical deficiency lies in the absence of proper access control checks when processing requests to fetch these financial records. Instead of validating whether the requesting user has explicit permission to view specific document types or individual record instances, the system blindly returns the requested data based solely on the existence of the resource identifier provided by the client. This design oversight allows any authenticated entity interacting with this endpoint to bypass standard role-based access controls that are typically enforced elsewhere in the application logic.
The operational impact of this vulnerability is significant for organizations relying on ERPNext for financial management and enterprise resource planning. Because the flaw permits arbitrary document type selection, an attacker can target sensitive accounting records such as invoices, purchase orders, or payment entries that they would otherwise be denied access to under normal circumstances. This capability effectively transforms a standard authenticated user into a potential data exfiltration vector. Even users with minimal privileges, including portal users who typically have restricted views and individuals assigned no specific roles beyond basic authentication, can exploit this endpoint to read tax rows and associated financial metadata from documents outside their authorized scope. The exposure of detailed tax information not only compromises the confidentiality of sensitive business data but also aids attackers in mapping internal financial structures and identifying high-value targets for further exploitation or social engineering attacks.
From a classification perspective, this vulnerability aligns with CWE-285 Improper Authorization, as the application fails to enforce proper access controls on a protected resource. It is directly exploitable via HTTP requests that manipulate document identifiers without triggering secondary permission checks, which corresponds to ATT&CK technique T1078 Valid Accounts when leveraged by low-privilege users or T1005 Data from Local System if the data is extracted for offline analysis. The lack of record-level permissions checking means that even though a user may be authenticated, they are not subjected to the granular access policies designed to protect specific financial records within the ERP system.
To mitigate this vulnerability, organizations must immediately upgrade their Frappe ERPNext instances to version 15.122.0 or later for legacy deployments and version 16.50.0 or later for current deployments where these fixes have been implemented. Until an upgrade is feasible, administrators should consider implementing network-level controls such as web application firewalls that can detect and block anomalous requests targeting the affected Accounts module endpoints with unusual document type parameters. Additionally, reviewing user roles to ensure that portal users and low-privilege accounts do not require access to financial modules where possible will reduce the attack surface. It is also critical to audit logging mechanisms to monitor for repeated attempts by single IP addresses or user sessions to fetch disparate document types, which may indicate active exploitation of this authorization bypass.