CVE-2026-134373 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 14.0.0 before 15.121.0 and 16.x before 16.34.0 contains a missing authorization vulnerability in a Utilities module endpoint that lets any authenticated user retry failed bulk transactions without a role check. Attackers, including portal users with no roles, can send crafted requests for a chosen date to mark site-wide failed bulk transactions as retried, removing them from the normal recovery path, and add background job load.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Frappe ERPNext versions 14.0.0 prior to 15.121.0 and version 16.x prior to 16.34.0 represents a critical failure in access control mechanisms within the application's Utilities module. Specifically, an endpoint designed for retrying failed bulk transactions lacks proper authorization checks, allowing any authenticated user to execute this function regardless of their assigned roles or permissions. This flaw is particularly severe because it affects portal users who typically possess no administrative privileges and are restricted from performing sensitive operational tasks. By exploiting this missing role check, attackers can manipulate the state of system-wide data processing workflows without requiring elevated access rights, thereby bypassing fundamental security boundaries established by the application's permission model.
From a technical perspective, the core issue lies in the absence of validation logic that verifies whether the requesting user has the necessary privileges to trigger bulk transaction retries. In secure software design, operations that affect system-wide state or performance should be gated behind strict role-based access control lists. The vulnerable endpoint accepts requests for specific dates and processes them without verifying if the initiator is authorized to perform such actions. This allows malicious actors to send crafted HTTP requests targeting arbitrary date ranges, effectively instructing the backend to mark a wide array of failed bulk transactions as retried. Consequently, these transactions are removed from the standard recovery queue where they might have been monitored or handled by system administrators with appropriate oversight capabilities.
The operational impact of this vulnerability extends beyond simple data manipulation and introduces significant risks related to service availability and resource exhaustion. By forcing the retry mechanism on a site-wide scale for chosen dates, an attacker can generate a substantial volume of background jobs. This artificial inflation of workload places undue pressure on system resources such as CPU, memory, and database connections. In environments where ERPNext handles critical business operations, this uncontrolled generation of background tasks can lead to performance degradation, latency spikes, or even complete service denial for legitimate users. The ability to disrupt the normal flow of transaction processing undermines the reliability and stability of the enterprise resource planning system, potentially causing data inconsistencies if transactions are retried in an unintended state or sequence.
This vulnerability aligns with CWE-284, which describes Improper Access Control, specifically highlighting failures where authorization checks are omitted for critical functions. Furthermore, it maps to MITRE ATT&CK technique T1078, Valid Accounts, as the exploitation relies on using legitimate but low-privileged credentials to perform actions outside their intended scope. The scenario also reflects aspects of T1496, Resource Hijacking, due to the potential for consuming excessive system resources through malicious background job generation. To mitigate this risk, immediate patching is required by upgrading Frappe ERPNext to version 15.121.0 or later, and for version 16.x users, updating to at least version 16.34.0 ensures that the authorization checks are properly enforced on the Utilities module endpoints. Additionally, organizations should implement network-level monitoring to detect unusual spikes in background job creation from low-privileged accounts as a compensating control while updates are being deployed.