CVE-2026-134375 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 13.0.0 before 15.124.0 and 16.x before 16.52.0 contains an incorrect authorization vulnerability in an Accounts module endpoint that returns Payment Entries for a readable bank record without checking read permission on each Payment Entry. Authenticated users with an Accounts role can request a readable record to obtain metadata of Payment Entries excluded by their user permissions, such as Cost Center restrictions.

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 identified vulnerability represents a critical failure in access control logic within the Frappe ERPNext framework, specifically affecting versions 13.0.0 through 15.124.0 and version 16.x prior to release 16.52.0. This flaw is located in an endpoint associated with the Accounts module that is designed to retrieve Payment Entry records linked to a specific bank record. The core technical deficiency lies in the server-side authorization mechanism, which performs a permission check only on the parent Bank Record object rather than iterating through and validating access rights for each individual child Payment Entry returned in the response payload. This architectural oversight allows authenticated users possessing an Accounts role to bypass granular user permissions that would normally restrict their visibility into specific financial data segments.

From a technical perspective, this vulnerability is classified under CWE-285, which describes Improper Authorization, and more specifically aligns with CWE-639 regarding authorization bypass through indirect reference or insufficient check on related objects. In typical ERP systems like Frappe, user permissions are often configured at the document level to enforce data segregation based on attributes such as Cost Center, Department, or Project. When a user queries for Payment Entries associated with a bank account they can view, the system correctly verifies that the user has read access to that Bank Record. However, it fails to apply the same rigorous permission filtering logic to each individual Payment Entry contained within the result set. Consequently, if a user lacks explicit permission to view certain Cost Centers or specific transaction types, those restrictions are ignored for any Payment Entries linked to an accessible bank record, leading to unauthorized data exposure.

The operational impact of this vulnerability is significant in environments where strict financial data segregation is required. An attacker with valid credentials and the Accounts role can exploit this endpoint to enumerate sensitive financial metadata that should be hidden from their user profile. This includes details such as transaction amounts, dates, counterparty information, and internal cost allocations associated with restricted Cost Centers. Such exposure violates principles of least privilege and confidentiality, potentially enabling further attacks or providing competitive intelligence if exposed externally. In regulated industries where audit trails and data privacy are paramount, this flaw could lead to compliance violations related to the unauthorized disclosure of financial records.

Mitigation strategies must focus on patching the underlying framework code to enforce row-level security checks for all child objects returned by API endpoints. Administrators should immediately upgrade Frappe ERPNext to version 15.124.0 or later, and for version 16.x users, they must update to at least release 16.52.0 where this authorization logic has been corrected. Until the patch is applied, organizations can implement compensating controls by restricting access to the specific API endpoint via network-level firewalls or WAF rules if possible, although this is less effective than a code fix. Additionally, auditing user permissions and ensuring that no unnecessary broad Accounts roles are assigned to users who do not require full financial visibility can help reduce the attack surface. Regular security assessments should include testing for indirect object reference flaws in all data retrieval endpoints to prevent similar authorization bypasses in other modules.

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 want to use VulDB in your project?

Use the official API to access entries easily!