CVE-2026-134398 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext 15.87.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that changes Period Closing Voucher job status without permission checks and accepts a request method triggerable cross-site. Authenticated users without an Accounts role, or cross-site pages opened by authenticated users, can send requests naming a scheduled job to stop accounting jobs from completing.
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 vulnerability identified in Frappe ERPNext versions prior to 15.121.4 and 16.x prior to 16.36.0 represents a critical failure in access control mechanisms within the Accounts module, specifically targeting endpoints responsible for managing Period Closing Voucher jobs. This flaw is classified as an Insecure Direct Object Reference combined with Cross-Site Request Forgery characteristics, allowing unauthorized actors to manipulate system state without proper authentication checks or authorization validation. The core technical issue lies in the server-side logic which fails to verify whether the requesting user possesses the necessary Accounts role permissions before executing commands that alter the status of scheduled accounting jobs. This absence of robust permission verification creates a direct path for attackers to interfere with critical financial processes, undermining the integrity and reliability of enterprise resource planning operations.
From an operational perspective, this vulnerability enables authenticated users who lack specific administrative or accounts-related roles to disrupt ongoing accounting workflows. By exploiting the missing authorization check, these users can send requests that force the termination or modification of Period Closing Voucher jobs. This capability effectively halts essential financial reporting and reconciliation tasks, potentially leading to data inconsistencies, delayed financial close processes, and significant operational disruptions within an organization. Furthermore, because the vulnerability accepts request methods triggerable via cross-site interactions, it introduces a severe risk of Cross-Site Request Forgery attacks. An attacker could craft malicious web pages or links that, when visited by an authenticated user with valid session cookies, automatically submit these unauthorized requests to the ERPNext server without the user's knowledge or consent.
The exploitation vector is particularly dangerous because it does not require complex privilege escalation techniques beyond basic authentication. Any logged-in user, regardless of their assigned role hierarchy within the application, can trigger this vulnerability if they are tricked into visiting a malicious site or clicking a crafted link. This cross-site capability amplifies the threat landscape significantly, as social engineering tactics become viable attack methods. The impact extends beyond simple service disruption; it compromises the trustworthiness of financial data by allowing unauthorized interference with period closing procedures, which are foundational to accurate financial statement generation and regulatory compliance.
This vulnerability aligns closely with CWE-269, Improper Privilege Assignment, as the system fails to enforce role-based access controls on sensitive administrative functions. Additionally, it maps to ATT&CK technique T1534, Internal Spearphishing, due to its susceptibility to cross-site request forgery attacks that rely on deceiving authenticated users into performing unintended actions. The lack of anti-CSRF tokens or same-origin policy enforcement in the affected endpoints further exacerbates this risk profile.
To mitigate this vulnerability, organizations must immediately upgrade Frappe ERPNext to version 15.121.4 or later for the v15 branch, and version 16.36.0 or later for the v16 branch. These updates contain patches that enforce strict authorization checks on all endpoints related to Period Closing Voucher job management. In addition to upgrading, administrators should implement robust Cross-Site Request Forgery protections, such as synchronizer token patterns, in custom modules if any legacy code remains unpatched temporarily. It is also advisable to review and tighten role-based access policies within the ERPNext interface to ensure that only designated accounting personnel have permissions related to financial job management. Regular security audits of API endpoints should be conducted to detect similar authorization flaws across other modules before they can be exploited in production environments.