/

CVE-2026-72910

Severity:

HIGH RISK

(7.1)

Missing Authorization (CWE-862) in ERPNext Account APIs

CVE-2026-72910

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized modification of protected business data and privilege boundary bypass

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

ERPNext contains missing authorization checks in several account, payment, purchasing, and cost-center functions. An authenticated limited user may exploit these gaps to modify protected data outside the permissions assigned to their role.

Affected context

The issue occurs in ERPNext deployments where authenticated users can reach affected server-side functions without the required write-permission enforcement. Relevant functionality includes account merging, job control for documents, release-date changes, payment reconciliation processing, and cost-center updates across the accounts and purchasing components.

Exploit preconditions

  • Attack surface: Authenticated ERPNext application endpoints or server-side function calls exposing the affected operations
  • Required access: A valid account with limited privileges and the ability to invoke or reach an affected function
  • Trigger point: Execution of one of the affected account, payment, purchase-invoice, job-control, release-date, or cost-center operations
  • Why exploitation is possible: Required write authorization checks are omitted, allowing role-limited users to perform actions normally restricted to users with broader permissions

Why this happens

The underlying defect is an authorization enforcement gap. Affected functions perform state-changing operations without consistently verifying whether the requesting user has the required write permission for the target document or data object. This maps to CWE-862: Missing Authorization, where access controls are absent or not applied at a security-sensitive operation.

Potential impact

  • Unauthorized changes to accounts, invoices, payment records, or cost centers may occur
  • Protected document data may be modified outside established role boundaries
  • Accounting records or operational workflows could be manipulated
  • Data integrity, auditability, and financial reporting may be affected
  • An attacker could use repeated unauthorized actions to broaden business impact

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every state-changing operation rather than relying only on interface visibility or client-side restrictions.

Common defensive patterns include:

  • Apply server-side write-permission checks immediately before modifying protected records
  • Reuse centralized authorization and document-permission mechanisms where available
  • Validate both the requested operation and the specific target document or data scope
  • Avoid treating authenticated identity alone as sufficient authorization
  • Apply least-privilege roles and minimize access to sensitive accounting functions
  • Record security-relevant authorization decisions and rejected modification attempts
  • Use secure-by-default API policies that deny unauthorized actions unless explicitly permitted

How teams detect issues like this

Organizations can identify similar authorization gaps through:

  • Static analysis and code review rules that flag state-changing functions without authorization calls
  • Review of server-side handlers that trust UI-level permission controls
  • Tests covering permitted, denied, and cross-role access for every affected operation
  • Monitoring for unusual modifications by limited-role accounts
  • Policy enforcement requiring authorization checks before database writes or document updates
  • Automated security review tools that compare endpoint behavior against role and permission matrices

Sources

SourceLink
github.comgithub.com/frappe/erpnext/commit/2ae6451f10926bd12b6ce6c7dc40f08da83f2460
github.comgithub.com/frappe/erpnext/commit/8c7a313a38dfe38c9e35ca41e91389bcfaed2404
github.comgithub.com/frappe/erpnext/commit/ba936eefabb784805daa4c602b4baec9fc243ff8
github.comgithub.com/frappe/erpnext/pull/55709
github.comgithub.com/frappe/erpnext/releases/tag/v15.112.0
github.comgithub.com/frappe/erpnext/releases/tag/v16.22.0
github.comgithub.com/frappe/erpnext/security/advisories/GHSA-qpvh-75wh-j645

Frequently asked

questions

It may be exploitable through the ERPNext application interface or callable server-side operations when those functions are exposed to an authenticated user.

The attacker generally needs a valid ERPNext account with enough access to reach an affected operation. Administrative privileges should not be required when the missing checks allow limited users to bypass their assigned permissions.

Enforce server-side authorization and target-document write checks at every affected state-changing function, using centralized permission logic where possible.

Maintain explicit role and permission tests, deny unauthorized operations by default, review all write paths during code changes, and monitor sensitive modifications by low-privilege accounts.

Find out what's already
exploitable in your codebase.