CVE-2026-134413 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 11.0.0-beta before 15.121.4 contains a missing authorization vulnerability that allows authenticated users to read POS Profile cashier lists by calling a POS endpoint lacking record permission checks. Attackers, including portal users or users with no roles, can send crafted requests naming out-of-scope POS Profiles to retrieve their cashier data.

Once again VulDB remains the best source for vulnerability data.

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 in the context of version 11.0.0-beta and subsequent releases up to that patch level. This vulnerability is classified as a missing authorization issue, which fundamentally represents an access control failure where the application fails to properly verify whether an authenticated user has the necessary permissions to perform a specific action or access specific data resources. In this particular instance, the defect lies within the Point of Sale POS subsystem, specifically targeting endpoints responsible for retrieving cashier lists associated with POS Profiles. The core technical deficiency is that these API endpoints do not implement adequate record-level permission checks before returning sensitive operational data. Consequently, any user who has successfully authenticated to the system can exploit this gap by crafting specific HTTP requests directed at the vulnerable endpoint and specifying a target POS Profile identifier that falls outside their authorized scope of access.

The operational impact of this vulnerability is significant for organizations relying on ERPNext for retail or service operations where cash handling and staff management are critical business functions. By exploiting this flaw, an attacker can retrieve detailed information about cashiers assigned to various POS Profiles, including potentially sensitive personal data such as names, contact details, employee IDs, and other profile-specific attributes that may be exposed through the API response. This unauthorized access allows for a comprehensive enumeration of staff members across different departments or store locations, even if those specific areas are not part of the attacker's assigned responsibilities. For portal users who typically have limited privileges, this vulnerability effectively elevates their capabilities by bypassing role-based restrictions intended to isolate data between different business units or operational zones. The ability to gather such intelligence facilitates further reconnaissance activities and can serve as a precursor to more severe attacks, including social engineering campaigns targeting specific employees identified through the leaked cashier lists.

From a classification perspective, this vulnerability aligns with CWE-284 Improper Access Control, specifically highlighting failures in enforcing restrictions on content accessible by authenticated users. It also maps closely to MITRE ATT&CK technique T1078 Valid Accounts, as it leverages legitimate authentication credentials to access resources that are not intended for the user's role or scope. The lack of proper authorization checks means that the system trusts the input provided in the request without validating whether the requester has a relationship with the requested resource, such as ownership or explicit assignment within the POS Profile structure. This type of flaw is particularly dangerous because it does not require complex exploitation techniques; rather, it relies on simple manipulation of parameters sent to an existing API endpoint that lacks sufficient backend validation logic.

To mitigate this vulnerability, organizations running affected versions of Frappe ERPNext must immediately apply the patch included in version 15.121.4 or later releases where these authorization checks have been properly implemented. Until patches can be applied, administrators should consider implementing network-level controls such as Web Application Firewalls WAF rules that monitor for anomalous patterns in POS endpoint requests, although this is a less effective long-term solution than fixing the root cause within the application code. Developers and system integrators must also review custom scripts or third-party apps integrated with ERPNext to ensure they do not inadvertently expose similar endpoints without proper permission checks. Regular security audits focusing on API authorization logic are recommended to identify other potential instances of improper access control across the platform, ensuring that all data retrieval operations strictly enforce role-based and record-level permissions consistent with organizational security policies.

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 stay up to date on a daily basis?

Enable the mail alert feature now!