CVE-2026-134429 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in a CRM and Support module endpoint that returns Communications of documents without checking whether the caller may read them. Authenticated attackers with a common operational role can send crafted requests naming out-of-scope records to read their email communications and relink them away from their original documents.

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.121.4 and 16.x prior to 16.36.0 represents a critical failure in access control mechanisms within the CRM and Support modules. This flaw specifically affects endpoints responsible for retrieving communications associated with various documents, such as sales orders, customer issues, or support tickets. The core technical deficiency lies in the absence of proper authorization checks when processing requests to list these communications. Instead of verifying whether the authenticated user has permission to view the specific document linked to a communication record, the system blindly returns data based on the provided identifier. This design oversight allows any authenticated user with minimal privileges to bypass intended security boundaries and access sensitive information that should remain restricted to authorized personnel or specific roles within the organization.

From an operational perspective, this missing authorization vulnerability enables attackers to perform unauthorized data disclosure attacks. By crafting HTTP requests that specify identifiers for documents outside their scope of authority, users can retrieve email communications related to those records. This exposure is particularly severe in enterprise environments where CRM and support modules handle confidential customer interactions, proprietary business discussions, or sensitive personal data protected under regulations such as GDPR or HIPAA. The ability to read these communications compromises the confidentiality integrity of the system, potentially leading to intellectual property theft, competitive intelligence gathering by insiders with low-level access, or further social engineering attacks leveraging leaked internal correspondence.

Beyond simple information disclosure, the vulnerability also facilitates a relinking attack vector. Attackers can not only view but also manipulate the metadata associated with these communications by relinking them away from their original documents to records they do control or have visibility into. This action disrupts audit trails and data integrity within the ERP system. It complicates forensic analysis during security incidents because communication history becomes fragmented or misattributed, undermining trust in the system's record-keeping capabilities. Such manipulation can be used to cover up malicious activities or create confusion regarding responsibility for specific business transactions.

This vulnerability aligns with CWE-284, which describes Improper Access Control, specifically highlighting failures where access control decisions are not enforced correctly during resource retrieval operations. In terms of the MITRE ATT&CK framework, this behavior maps directly to T1078 Valid Accounts and potentially T1530 Data from Cloud Storage if the communications contain external data artifacts. The exploitation requires authenticated access with a common operational role, indicating that even standard users without administrative privileges can exploit this flaw, which significantly expands the attack surface compared to vulnerabilities requiring high-level permissions.

Mitigation strategies must prioritize immediate patching of Frappe ERPNext to version 15.121.4 or later for the v15 branch and version 16.36.0 or later for the v16 branch, as these releases contain the necessary code corrections to enforce proper authorization checks on communication endpoints. In environments where patching is delayed due to stability concerns, temporary compensating controls should be implemented at the network perimeter using Web Application Firewalls (WAF) to detect and block anomalous requests that attempt to access resource identifiers inconsistent with user roles or previous session activity. Additionally, organizations should review their role-based access control policies within ERPNext to ensure that data visibility is strictly scoped according to the principle of least privilege, minimizing the potential impact if similar vulnerabilities are discovered in other modules. Regular security audits and penetration testing focused on API endpoints are recommended to identify further gaps in authorization logic across the application suite.

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!