CVE-2026-134433 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext before 15.124.2 and 16.x before 16.53.0 fails to enforce record-level authorization in several endpoints, reports and forms, allowing authenticated low-privilege users to access data beyond their role. Attackers can send crafted requests naming out-of-scope records to read other companies' financial, stock, pricing and contact data or make constrained changes to those 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 vulnerability identified in Frappe ERPNext versions prior to 15.124.2 and 16.x prior to 16.53.0 represents a critical failure in the application's access control mechanisms, specifically concerning record-level authorization. This flaw allows authenticated users with low-privilege roles to bypass intended security restrictions and interact with data that falls outside their authorized scope. The core technical issue lies in how specific endpoints, reports, and forms within the ERPNext framework validate user permissions against requested resources. Instead of strictly enforcing role-based access control at the individual record level, the application relies on insufficient checks that can be circumvented by manipulating request parameters to target out-of-scope records. This architectural weakness means that while a user may have legitimate access to certain modules or general data sets, they are not properly restricted from accessing specific instances of those datasets belonging to other organizations or entities within the multi-tenant environment.

From an operational perspective, this vulnerability poses severe risks to data confidentiality and integrity across multiple companies sharing the ERPNext instance. Attackers can exploit these misconfigured endpoints by sending crafted HTTP requests that specify identifiers for records they are not authorized to view. Successful exploitation enables the unauthorized reading of sensitive financial information, including invoices, payment entries, and general ledger details, as well as stock levels, pricing structures, and contact data associated with other companies. Beyond mere data exfiltration, the vulnerability also permits constrained modifications to these out-of-scope records. This capability allows attackers to alter critical business data such as inventory counts or financial figures, potentially leading to significant operational disruptions, financial loss, and compromised audit trails for affected organizations.

This type of flaw is classically categorized under CWE-284 Improper Access Control, specifically reflecting a failure in object-level permission checks where the application does not verify that the authenticated user has explicit rights to access or modify the specific resource instance being targeted. In terms of adversary behavior mapping within the MITRE ATT&CK framework, this vulnerability facilitates several tactics including Initial Access through legitimate credentials, Credential Access if combined with other flaws, and more critically Data Exfiltration via API endpoints as well as Impact through data manipulation. The ability to read sensitive financial and contact data aligns with techniques used for reconnaissance and collection of valuable intelligence, while the capacity to make changes impacts system integrity and availability by corrupting business-critical records.

To mitigate this vulnerability, organizations running Frappe ERPNext must immediately upgrade their instances to version 15.124.2 or later if on the v15 branch, or version 16.53.0 or later for the v16 branch, as these releases contain patches that enforce stricter record-level authorization checks. Until an upgrade is feasible, administrators should review custom scripts and API integrations to ensure they do not expose sensitive endpoints unnecessarily. Implementing additional network-layer controls such as Web Application Firewalls can provide a temporary layer of defense by monitoring for anomalous request patterns indicative of IDOR attempts. Furthermore, conducting regular security audits focused on role-based access control configurations helps identify other potential weaknesses in permission assignments across the ERP system to ensure that data segregation between tenants remains robust and uncompromised.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!