CVE-2026-134381 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in the Buying module: the endpoint that closes and reopens Purchase Orders checks only document-type write permission, not per-document User Permissions. Authenticated users with Purchase Order write access can send crafted requests naming another company's Purchase Order to change its status.

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 security flaw resides within the Frappe ERPNext framework, specifically affecting versions prior to 15.121.4 and version 16.x prior to 16.36.0. This vulnerability is classified as an incorrect authorization issue located in the Buying module of the enterprise resource planning software. The core technical deficiency lies in how the system validates access control when processing requests to close or reopen Purchase Orders. Instead of enforcing granular, per-document User Permissions that restrict actions based on specific ownership or organizational boundaries, the endpoint relies solely on a broad document-type write permission check. This architectural oversight allows authenticated users who possess general write privileges for Purchase Order documents to bypass intended security controls by targeting resources they do not own.

From an operational perspective, this vulnerability enables unauthorized modification of critical business records belonging to other entities within the same multi-tenant or organizational setup. An attacker with valid credentials and basic purchase order writing rights can craft specific HTTP requests that target a Purchase Order associated with a different company. By manipulating these requests, the attacker can alter the status of external documents, such as marking them as closed when they should remain open, or reopening orders that have been finalized. This capability undermines data integrity and confidentiality, potentially leading to significant financial discrepancies, disrupted supply chain operations, and compromised audit trails within the ERP system.

This vulnerability aligns with CWE-269, which describes Improper Privilege Management, as well as CWE-862, Missing Authorization, because the application fails to enforce proper access control policies on specific resources. In terms of adversary tactics, this behavior corresponds to MITRE ATT&CK technique T1078, Valid Accounts, where an attacker leverages legitimate credentials to perform unauthorized actions due to flawed permission logic. The exploitation does not require complex injection techniques or buffer overflows but rather a precise understanding of the API structure and privilege escalation paths inherent in the framework's authorization model.

To mitigate this risk, organizations running affected versions must immediately upgrade Frappe ERPNext to version 15.121.4 or later for the v15 branch, or version 16.36.0 and above for the v16 branch. These updates contain patches that enforce strict per-document User Permissions during status changes, ensuring that users can only modify documents they are explicitly authorized to access based on their assigned roles and permissions. Additionally, administrators should review existing user roles within the Buying module to ensure that write privileges are granted with minimal necessary scope. Implementing regular security audits of permission sets and monitoring for anomalous activity in purchase order status changes can further enhance defense-in-depth strategies against such authorization bypasses.

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 know what is going to be exploited?

We predict KEV entries!