CVE-2026-134379 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 8.2.5 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in Manufacturing module endpoints that check only document-type write access, not permission on each Work Order. Authenticated users restricted by User Permissions can send crafted requests naming another company's Work Order to stop, resume or close it.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The identified vulnerability represents a critical failure in the implementation of role-based and user-specific access controls within the Frappe ERPNext framework, specifically affecting versions prior to 8.2.5 for the legacy branch and before 16.36.0 for the current release line. This flaw resides primarily within the Manufacturing module endpoints responsible for managing Work Orders, which are central to production planning and execution in enterprise resource planning systems. The core technical deficiency lies in the authorization logic used by these API endpoints, which performs a coarse-grained check against document-type write permissions rather than conducting fine-grained validation of individual record ownership or user-specific restrictions. In secure software design, particularly within multi-tenant environments where data isolation is paramount, access control mechanisms must verify that an authenticated entity possesses explicit permission for the specific resource instance being accessed, not merely general rights to interact with a particular object class.

From a technical perspective, this vulnerability allows for unauthorized modification of critical production data through insecure direct object references or broken access control patterns. When an authenticated user submits a request to stop, resume, or close a Work Order, the system validates whether that user has write permissions associated with the general Work Order document type. If such generic permission exists, which is common in many organizational setups where managers need oversight over production lines, the server proceeds to execute the state change on the specified identifier without verifying if the target Work Order belongs to an entity or company for which the requesting user holds specific User Permissions. This omission creates a direct path for privilege escalation and data manipulation by users who are intentionally restricted from viewing or altering records belonging to other divisions, subsidiaries, or external partner companies within the same ERP instance.

The operational impact of this flaw is severe in multi-company deployments where strict data segregation is required for compliance with regulations such as GDPR, HIPAA, or industry-specific standards like SOX and ISO 27001. An attacker leveraging this vulnerability can disrupt manufacturing operations by arbitrarily halting production lines belonging to other entities, leading to significant financial losses due to delayed deliveries and supply chain disruptions. Furthermore, the ability to close Work Orders prematurely may result in inaccurate inventory levels, flawed cost accounting, and compromised audit trails. Since ERPNext is often used as a centralized system for complex business processes, this lack of granular authorization undermines the integrity of the entire manufacturing workflow, potentially allowing malicious insiders or compromised accounts to cause widespread operational chaos across different organizational units sharing the same database instance.

This vulnerability aligns with CWE-269 Improper Privilege Management and CWE-862 Missing Authorization, reflecting a fundamental failure in enforcing least privilege principles at the object level. In terms of offensive security frameworks, it maps directly to MITRE ATT&CK technique T1078 Valid Accounts combined with T1530 Data from Cloud Storage Object Misconfiguration if viewed through the lens of data exfiltration or manipulation via API endpoints. The exploitation vector is straightforward and does not require complex payload construction beyond crafting HTTP requests that target specific Work Order identifiers belonging to unauthorized entities, making it highly exploitable by any authenticated user with basic scripting capabilities.

To mitigate this risk, organizations must immediately upgrade their Frappe ERPNext instances to version 8.2.5 or later for the older branch and version 16.36.0 or later for the current release line, where these authorization checks have been corrected to enforce granular User Permissions on individual Work Order records. In environments where upgrading is not immediately feasible due to compatibility constraints with custom apps or integrations, administrators should implement strict network-level controls such as Web Application Firewalls that monitor and restrict API calls based on user identity and target resource ownership. Additionally, reviewing existing role definitions to ensure that write permissions for the Manufacturing module are granted only to users who require broad access across all companies is essential. Regular security audits focusing on object-level authorization logic in custom modules can also help identify similar patterns of insufficient access control before they lead to significant breaches or operational disruptions.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!