CVE-2026-134393 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 10.1.41 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in a Manufacturing module endpoint that replaces BOMs without checking whether the caller may modify either BOM or the affected assemblies. Authenticated users who can create a BOM Update Log can send a crafted request naming two BOMs to replace the first with the second in every assembly site-wide.

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.122.0 and 16.x before 16.50.0 represents a critical failure in access control mechanisms within the Manufacturing module, specifically affecting endpoints responsible for Bill of Materials management. This flaw is classified as an Insecure Direct Object Reference or more accurately, a Broken Access Control vulnerability where the application fails to enforce proper authorization checks on sensitive operations. The core technical issue lies in the endpoint that facilitates BOM replacement, which allows authenticated users with specific permissions related to creating BOM Update Logs to execute state-changing actions without verifying their rights to modify the target Bill of Materials or the assemblies dependent upon it. This lack of granular permission validation enables an attacker who has obtained valid credentials for a user account with minimal privileges to perform administrative-level changes across the entire system.

From a technical perspective, the vulnerability exploits the logic that governs how BOM updates are propagated through the manufacturing hierarchy. When a request is crafted to replace one Bill of Materials with another, the server processes this instruction globally rather than restricting it to specific contexts or verifying ownership and modification rights for each affected assembly site-wide. This design oversight means that any authenticated user capable of initiating a BOM update log can manipulate the structural definitions used in production. By sending a specially constructed HTTP request specifying two distinct BOM identifiers, an attacker can force the system to substitute one set of manufacturing instructions with another across all relevant assemblies. This bypasses standard role-based access control protocols because the authorization check is either absent or incorrectly implemented for this specific high-impact operation.

The operational impact of this vulnerability is severe due to its potential to disrupt supply chain integrity and production workflows. An attacker could replace critical BOMs with maliciously crafted alternatives, leading to the procurement of incorrect materials, assembly errors, or even the introduction of defective components into finished products. In a manufacturing environment, such alterations can result in significant financial losses, delayed shipments, and quality control failures. Furthermore, because the change is applied site-wide, the scope of damage extends beyond individual projects to affect multiple production lines simultaneously. This lack of isolation between user actions and system state changes undermines the reliability of the ERPNext platform for organizations relying on precise manufacturing data integrity.

This vulnerability aligns with CWE-269, which covers Improper Privilege Management, as it allows a lower-privileged actor to perform functions that should be restricted to higher-privileged administrators or specific role holders. Additionally, from an offensive security perspective, this behavior is consistent with ATT&CK technique T1078, Valid Accounts, where adversaries use legitimate credentials to gain access and manipulate system configurations. The ability to alter core manufacturing data without proper authorization checks also touches upon CWE-926, Improper Export of Data with Excessive Privileges, in the context of modifying internal state rather than just reading it.

To mitigate this risk, organizations running affected versions of Frappe ERPNext must immediately upgrade to version 15.122.0 or later for the v15 branch, and version 16.50.0 or later for the v16 branch, where these access control checks have been implemented. Until an upgrade is feasible, administrators should review user roles and permissions within the Manufacturing module to ensure that only trusted personnel with explicit authorization can create BOM Update Logs. Implementing additional monitoring on manufacturing endpoints to detect unusual patterns of BOM replacement requests can also help in identifying potential exploitation attempts. Regular security audits focusing on access control logic for critical business functions are recommended to prevent similar vulnerabilities from persisting in enterprise resource planning systems.

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!