CVE-2026-134406 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 15.94.2 before 15.122.0 and 16.x before 16.50.0 contains an incorrect authorization vulnerability in a supplier portal endpoint whose party identity check ignores party type, failing to distinguish a Customer and a Supplier that share a name. Authenticated users, including portal users or users with no assigned roles, can send crafted requests naming records outside their permitted scope to read buying-portal records.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in Frappe ERPNext versions prior to 15.122.0 and 16.x prior to 16.50.0 represents a critical failure in access control mechanisms within the supplier portal functionality. This flaw is classified as an insecure direct object reference or broken access control, specifically falling under CWE-862 which denotes missing authorization checks. The core technical issue stems from how the application validates party identity when processing requests against specific endpoints designed for supplier interactions. Instead of strictly validating that the authenticated user's assigned role and associated data scope align with the requested resource type, the system relies primarily on a name-based matching logic. This approach fails to distinguish between different entity types, such as Customers and Suppliers, if they happen to share an identical name string within the database.

In operational terms, this architectural oversight allows authenticated users to bypass intended security boundaries. An attacker who has successfully authenticated to the ERPNext instance, regardless of whether they possess specific administrative roles or are merely a portal user with limited privileges, can manipulate request parameters to target records belonging to other party types. By crafting requests that specify a supplier record while authenticating as a customer entity (or vice versa) where both entities share the same name, the application incorrectly grants access. This results in the unauthorized reading of buying-portal records and sensitive business data that should remain isolated within specific operational silos. The vulnerability effectively neutralizes role-based access control measures by exploiting the ambiguity in identity resolution logic.

The impact of this vulnerability extends beyond simple data leakage to potential compliance violations and competitive intelligence risks. Since ERPNext is widely used for enterprise resource planning, it handles sensitive financial transactions, supplier contracts, pricing agreements, and procurement histories. Unauthorized access to buying-portal records could expose confidential vendor lists, negotiated prices, and supply chain logistics details. This aligns with the MITRE ATT&CK technique T1078 Valid Accounts, as the exploitation requires valid authentication credentials but leverages flawed authorization logic rather than credential theft or brute force attacks. Furthermore, it relates to T1530 Data from Cloud Storage Object if the underlying data is stored in cloud-backed object storage systems commonly integrated with such platforms.

Mitigation strategies must prioritize immediate patching of the ERPNext instance to version 15.122.0 or later for the v15 branch, and version 16.50.0 or later for the v16 branch, where this identity validation logic has been corrected to enforce strict type checking alongside name matching. In environments where immediate patching is not feasible due to operational constraints, network-level controls such as Web Application Firewalls can be configured to inspect request payloads and block attempts that exhibit patterns consistent with object reference manipulation. Additionally, organizations should review their user provisioning processes to ensure that role assignments are strictly audited and that the principle of least privilege is enforced across all portal users. Regular security assessments focusing on access control logic are recommended to identify similar weaknesses in other modules where entity types might be conflated based on shared attributes rather than unique identifiers or explicit type validation.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!