CVE-2026-134417 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 13.0.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns uploaded bank statement file content without checking record-level permissions. Authenticated attackers, including portal users or users with no assigned roles, can send crafted requests naming records outside their scope to read full statement file contents.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The identified vulnerability represents a critical failure in access control mechanisms within the Frappe ERPNext framework, specifically affecting versions 13.0.0 through 15.121.4 and version 16.x prior to release 16.36.0. This flaw is categorized as an Insecure Direct Object Reference or Broken Access Control vulnerability, which aligns with CWE-862 in the Common Weakness Enumeration taxonomy. The core technical issue resides within a specific endpoint of the Accounts module responsible for retrieving uploaded bank statement files. Instead of validating whether the requesting user possesses explicit permissions to access the targeted record, the system blindly serves the file content based solely on the identifier provided in the request payload. This architectural oversight allows any authenticated entity to bypass intended security boundaries by manipulating object references to target resources they are not authorized to view.

The operational impact of this vulnerability is severe due to its broad applicability across user roles within the ERPNext ecosystem. Unlike many access control flaws that require elevated privileges, this weakness can be exploited by portal users or individuals with no assigned roles at all, provided they have valid authentication credentials for any account on the system. Attackers can craft specific HTTP requests containing identifiers of bank statements belonging to other departments, clients, or competitors within the same instance. By doing so, they can exfiltrate sensitive financial data including transaction histories, vendor details, and internal accounting records without triggering standard security alerts associated with privilege escalation attempts. This capability effectively neutralizes the multi-tenant isolation guarantees that ERPNext relies upon for enterprise deployments.

From a threat modeling perspective, this vulnerability facilitates unauthorized data disclosure which is mapped to MITRE ATT&CK technique T1530 Data from Cloud Storage Object or potentially T1078 Valid Accounts if leveraged through compromised credentials. The exploitation chain typically involves the attacker enumerating valid record IDs and submitting them via API calls designed for authorized users, thereby harvesting confidential financial information that could be used for further social engineering attacks, corporate espionage, or regulatory non-compliance penalties under frameworks such as GDPR or SOX.

Mitigation strategies must prioritize immediate patching to the latest stable versions of ERPNext where this authorization check has been implemented correctly. In environments where upgrading is not immediately feasible, network-level controls should be enforced to restrict access to the affected Accounts module endpoints only from trusted internal subnets and authenticated service accounts with verified role-based permissions. Additionally, implementing strict input validation on server-side handlers to verify user ownership against database records before serving file content will restore the intended security posture. Regular audits of API endpoint logic are recommended to detect similar patterns of missing authorization checks across other modules within 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

Interested in the pricing of exploits?

See the underground prices here!