CVE-2026-134374 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 15.0.0 before 15.124.0 and 16.x before 16.52.0 contains a missing authorization vulnerability in Assets module endpoints that return a depreciation schedule for a caller-supplied asset without checking read permission on that asset. Authenticated users can name another company's asset to disclose its purchase value, value after depreciation, and depreciation entries.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/21/2026

The identified security flaw resides within the Frappe ERPNext platform, specifically affecting versions 15.0.0 through 15.123.0 and version 16.x prior to release 16.52.0. This vulnerability is classified as a broken access control issue, formally recognized under Common Weakness Enumeration identifier CWE-862, which denotes missing authorization checks for critical functions. The core technical deficiency lies in the asset management module endpoints responsible for generating and returning depreciation schedules. When an authenticated user requests data regarding a specific asset by providing its unique name or identifier, the backend logic fails to verify whether that particular user possesses read permissions for the associated company's assets. This oversight allows any logged-in account, regardless of their role or assigned privileges within the system, to query details belonging to other organizations operating on the same instance.

The operational impact of this vulnerability is significant due to the sensitivity of the data exposed. By exploiting this missing authorization check, an attacker can retrieve comprehensive financial information for assets owned by competing companies or separate business units within a multi-tenant environment. The disclosed data includes the original purchase value, the current book value after depreciation calculations, and detailed records of all historical depreciation entries. This constitutes a severe breach of confidentiality, potentially revealing strategic investment decisions, asset lifecycle costs, and operational expenditures that are intended to be restricted to authorized finance or management personnel only. In environments where ERPNext is deployed as a shared service provider for multiple distinct legal entities, this flaw effectively breaks the isolation boundaries between tenants, allowing cross-company data leakage.

From an industry standard perspective, this vulnerability aligns with MITRE ATT&CK technique T1530, which covers Data from Cloud Storage Object Misconfiguration, although in this context it is more accurately mapped to unauthorized access of sensitive resources within a web application environment. The lack of proper object-level permission checks represents a fundamental failure in implementing the principle of least privilege and secure direct object references. Attackers can automate requests using simple scripts or manual testing tools to enumerate assets across different companies, aggregating financial data that could be used for competitive intelligence, fraud planning, or further social engineering attacks against targeted organizations.

To mitigate this vulnerability, immediate action is required by upgrading the ERPNext instance to version 15.124.0 or later, which includes patches addressing these authorization gaps in the assets module. For systems where an upgrade is not immediately feasible, administrators should implement strict network-level access controls and web application firewall rules that monitor for anomalous patterns of asset data retrieval across different company identifiers. Additionally, a thorough code review focusing on all endpoints within the Assets module is recommended to ensure that every request validates both user authentication and object-level authorization against the specific resource being accessed. Regular security audits should also be conducted to verify that permission checks are consistently applied across all API routes and internal function calls related to sensitive financial data.

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!