CVE-2026-134404 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 6.3.0 before 15.124.0 and 16.x before 16.52.0 contains a missing authorization vulnerability in the customer and supplier portal list endpoint, which returns complete selling documents and RFQs without checking permission on the requested records. Authenticated attackers, including portal users or users without roles, can request out-of-scope records to read valuation, margin, and other bidder details.

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 6.3.0 before 15.124.0 and version 16.x before 16.52.0 represents a critical failure in access control mechanisms within the customer and supplier portal interfaces. This flaw specifically affects the list endpoints responsible for retrieving selling documents, such as sales orders or invoices, and requests for quotations (RFQs). The core technical deficiency lies in the absence of proper authorization checks when processing these API requests. Instead of validating whether the authenticated user has permission to access specific records based on their role, permissions, or data ownership, the system returns complete datasets containing sensitive information associated with those documents. This design oversight allows any authenticated entity interacting with the portal endpoints to bypass intended security boundaries and retrieve data that should be restricted by default.

From a technical perspective, this vulnerability is classified as CWE-284 Improper Access Control, specifically falling under the sub-category of insufficient authorization checks for API resources. The impact extends beyond simple unauthorized access; it enables authenticated attackers, including portal users with limited privileges or even unauthenticated entities if session management is also compromised, to exfiltrate confidential business intelligence. By exploiting this endpoint, an attacker can retrieve detailed valuation metrics, profit margins, and competitive bidding details from RFQs intended for internal use only. This exposure compromises the confidentiality of critical financial data and strategic procurement information, potentially giving competitors or malicious insiders insight into pricing strategies and supplier negotiations that are meant to remain confidential within the organization's operational perimeter.

The operational impact of this vulnerability is significant for organizations relying on ERPNext for their enterprise resource planning needs. The leakage of valuation and margin details can directly affect competitive positioning in the market if such data falls into the hands of external competitors. Furthermore, the exposure of bidder information from RFQs undermines the integrity of procurement processes, potentially leading to bid-rigging or unfair advantages among suppliers who gain access to competing bids before they are officially released. For internal users with low-level permissions, this flaw effectively grants them elevated privileges without any additional authentication steps, violating the principle of least privilege and complicating compliance efforts for industries subject to strict data governance regulations such as GDPR or SOX where financial data confidentiality is mandated.

Mitigation strategies must prioritize immediate patching to the specified safe versions, specifically upgrading Frappe ERPNext to version 15.124.0 or later in the 6.x branch and version 16.52.0 or later in the 16.x branch. These updates contain the necessary code changes to enforce rigorous authorization checks on all list endpoints related to selling documents and RFQs. In addition to patching, organizations should implement robust input validation and ensure that API responses are filtered based on the requesting user's explicit permissions before data is serialized and returned. Security teams should also conduct audits of their ERPNext deployments to identify any customizations or third-party apps that might bypass these standard security controls. Continuous monitoring for anomalous access patterns to customer and supplier portals can help detect exploitation attempts in real-time, providing an additional layer of defense while the underlying vulnerability remains unpatched during transition periods. This incident underscores the importance of integrating automated security testing into the development lifecycle to catch such authorization flaws before they reach production environments.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!