CVE-2026-134403 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 7.0.0 before 15.124.0 and 16.x before 16.52.0 contains a missing authorization vulnerability in the customer portal Projects list, which returns every field without checking permission on the requested records. Authenticated users, including portal users or users with no assigned roles, can send crafted requests naming out-of-scope records to read project costing and margin data.
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.124.0 in the legacy branch and before version 16.52.0 in the current release line. This vulnerability is classified as a missing authorization issue, which fundamentally represents a failure of the application to enforce proper access controls on sensitive resources. In secure software architecture, every request for data must be validated against the permissions associated with the authenticated user's identity and assigned roles. However, in this specific instance, the customer portal interface responsible for listing projects fails to perform these critical checks before returning data to the client side. This architectural oversight allows any authenticated entity interacting with the system to bypass intended security boundaries that should restrict access based on project ownership or departmental affiliation.
The technical mechanism of exploitation involves an attacker sending crafted HTTP requests targeting specific record identifiers within the Projects list endpoint. Because the backend logic does not verify whether the requesting user has permission to view the details of a particular project, it proceeds to serialize and return all available fields associated with that record. This behavior is particularly dangerous because ERPNext projects often contain highly sensitive financial information, including detailed cost breakdowns, budget allocations, profit margins, and client billing rates. The absence of server-side validation means that an attacker does not need complex privilege escalation techniques; they simply need to iterate through or guess valid project IDs to extract data from records that are strictly out-of-scope for their user profile. This constitutes a classic Broken Access Control scenario where the system trusts input identifiers without validating them against access control policies.
The operational impact of this vulnerability is severe, primarily due to the nature of the exposed data. Project costing and margin information represents core competitive intelligence and financial health metrics for an organization. Unauthorized disclosure of such data can lead to significant business harm, including loss of competitive advantage if pricing strategies are revealed to competitors or clients. Furthermore, it violates principles of confidentiality required by many regulatory frameworks governing financial data protection. For organizations using ERPNext as their central enterprise resource planning tool, this leak undermines trust in the system's ability to isolate sensitive departmental or client-specific information. Even users with minimal privileges or no specific role assignments can exploit this flaw, expanding the attack surface significantly beyond just high-privileged administrators and including any registered portal user who might have low-level access for basic tasks like viewing their own limited projects.
From a classification perspective, this vulnerability aligns directly with CWE-284, which describes Improper Access Control, specifically highlighting failures in authorization checks before granting access to resources. It also maps closely to the MITRE ATT&CK technique T1078, Valid Accounts, as it leverages legitimate authentication credentials to perform unauthorized data exfiltration. The attack pattern resembles a horizontal privilege escalation where an attacker accesses data belonging to other users or entities within the same permission tier rather than escalating their own privileges vertically. This type of vulnerability is often difficult to detect through standard functional testing because the application appears to work correctly for authorized records, only failing when out-of-scope identifiers are introduced into the request payload.
To mitigate this risk, organizations running affected versions must immediately upgrade Frappe ERPNext to version 15.124.0 or later, or version 16.52.0 and above, where these authorization checks have been implemented in the backend logic. Until an upgrade is feasible, administrators should consider implementing network-level controls such as Web Application Firewalls that can detect anomalous patterns of record ID enumeration if possible, although this is a less reliable defense than patching the application code directly. Additionally, it is advisable to review user roles and permissions within the ERPNext instance to ensure that portal users have only the minimum necessary access rights, reducing the potential blast radius should similar vulnerabilities exist elsewhere in the system. Regular security audits focusing on API endpoints and data retrieval mechanisms are recommended to identify other instances where authorization checks might be missing or insufficiently enforced across different modules of the platform.