CVE-2026-134392 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 15.0.0 before 15.122.0 and 16.x before 16.50.0 contains a missing validation vulnerability in a Stock module endpoint that fails to verify reserved item rows belong to the target Sales Order. Authenticated users with the Stock User role can send crafted reservation requests naming another order's item row to reserve stock beyond that order's limits, creating mismatched Stock Reservation Entries.

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 vulnerability identified in Frappe ERPNext versions prior to 15.122.0 and 16.x prior to 16.50.0 represents a critical logic flaw within the stock management subsystem, specifically affecting the Sales Order reservation endpoints. This issue stems from an insufficient validation mechanism that fails to enforce strict ownership constraints on inventory reservations. In enterprise resource planning systems like ERPNext, Stock Reservation Entries are designed to allocate specific quantities of items to particular sales orders, ensuring that available stock is reserved for confirmed customer commitments and preventing overselling or allocation conflicts. The core technical flaw lies in the backend API endpoint responsible for processing these reservation requests, which accepts parameters defining the item row and target order but does not adequately verify that the requested item row actually belongs to the specified Sales Order identifier provided by the user.

From a technical perspective, this is classified as an Insecure Direct Object Reference combined with Broken Access Control, aligning closely with CWE-602 (Client-Side Enforcement of Server-Side Access Control) and CWE-918 (Server-Side Request Forgery if applicable via indirect object references), though primarily it falls under CWE-284: Improper Access Control. The vulnerability allows an authenticated user possessing the Stock User role to manipulate internal identifiers or row indices associated with different sales orders. By crafting a malicious request that specifies a reserved item row from one Sales Order while claiming it belongs to another, the attacker can bypass logical checks intended to isolate inventory allocations per order. This lack of server-side validation means the application trusts client-supplied data regarding object ownership without cross-referencing against database records to confirm association integrity.

The operational impact of this vulnerability is significant for organizations relying on ERPNext for supply chain and sales management. An attacker can create mismatched Stock Reservation Entries, effectively reserving stock intended for one customer order under the guise of another. This leads to data inconsistency where inventory levels are artificially reduced or allocated incorrectly, potentially causing fulfillment delays, shipping errors, or financial discrepancies when invoices are generated based on incorrect reservation states. Furthermore, this manipulation could be leveraged in conjunction with other vulnerabilities to escalate privileges or disrupt business operations by creating phantom reservations that block legitimate stock availability for valid orders. The ability to decouple item rows from their parent sales order undermines the integrity of inventory tracking and breaks the audit trail essential for accurate financial reporting.

Mitigation strategies must prioritize immediate patching as well as defensive coding practices. Organizations should upgrade Frappe ERPNext to version 15.122.0 or later, or version 16.50.0 and above, where this validation logic has been corrected to ensure that every reservation request is rigorously checked against the database to confirm that the item row indeed belongs to the target Sales Order before processing. In environments where immediate patching is not feasible, temporary mitigations include restricting access to the affected Stock module endpoints via network-level controls or web application firewalls if possible, and enforcing strict role-based access control policies to limit who can interact with stock reservation APIs. Additionally, implementing server-side validation that cross-references all object identifiers against their parent entities before processing is a critical best practice recommended by industry standards such as OWASP Top 10 under Broken Access Control categories to prevent similar logic flaws in future development cycles.

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!