CVE-2026-134435 in ERPNext
Summary
by MITRE • 11/21/2026
Frappe ERPNext before 15.124.2 and 16.x before 16.50.0 contains a missing authorization vulnerability in an Accounts module endpoint that records bank clearance dates, which checks only a broad role permission before writing to caller-named payment documents. Authenticated Accounts Users can send crafted requests naming payment documents of other companies, outside their User Permissions, or already submitted, to alter clearance dates and compromise bank reconciliation integrity.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Frappe ERPNext versions prior to 15.124.2 and 16.x prior to 16.50.0 represents a critical failure in access control mechanisms within the Accounts module, specifically affecting endpoints responsible for recording bank clearance dates. This flaw is classified as an Insecure Direct Object Reference (IDOR) or Broken Access Control issue, aligning with CWE-284 and corresponding to MITRE ATT&CK technique T1530, which involves data exfiltration from cloud storage through improper access controls. The core technical deficiency lies in the validation logic used when processing requests to update payment document clearance dates. Instead of verifying that the authenticated user has specific permissions for the target object based on its unique identifier or associated company context, the system performs only a broad role-based check. This means that as long as the requester possesses the generic Accounts User role, the application proceeds with the operation without confirming whether the user is authorized to modify the specific document in question.
This architectural oversight allows authenticated attackers who hold minimal privileges within the ERPNext environment to manipulate financial records belonging to other organizations or entities managed within the same instance. By crafting HTTP requests that specify payment documents outside their designated User Permissions, an attacker can alter clearance dates for transactions they do not own. Furthermore, the vulnerability extends to already submitted documents, which should typically be immutable without proper audit trails and elevated privileges. The ability to modify these records enables malicious actors to change the status of financial transactions from pending to cleared or vice versa, effectively bypassing standard workflow controls designed to prevent unauthorized alterations after submission.
The operational impact of this vulnerability is severe for organizations relying on ERPNext for accurate financial reporting and bank reconciliation processes. Bank reconciliation integrity relies heavily on the accuracy and immutability of transaction records linking internal ledger entries with external bank statements. By allowing unauthorized users to alter clearance dates, an attacker can create discrepancies between the company's books and actual bank balances. This manipulation can be used to conceal fraudulent transactions, hide embezzlement activities, or disrupt financial audits by making it difficult to trace the true timeline of fund movements. In multi-tenant deployments where multiple companies share a single ERPNext instance, this vulnerability poses an even greater risk as it facilitates cross-company data tampering, potentially leading to significant legal and regulatory compliance issues related to financial transparency and accountability.
To mitigate this vulnerability, organizations must immediately upgrade their Frappe ERPNext instances to version 15.124.2 or later for the v15 branch, or version 16.50.0 or later for the v16 branch, where these access control checks have been corrected. Until an upgrade is feasible, administrators should implement strict network-level controls such as Web Application Firewalls to monitor and restrict unusual patterns of requests targeting payment document endpoints. Additionally, it is crucial to review and tighten User Permissions within ERPNext, ensuring that users are granted the minimum necessary privileges required for their specific roles rather than relying solely on broad role assignments. Regular audits of bank reconciliation processes and monitoring for unexpected changes in clearance dates can also help detect potential exploitation attempts early.