Skip to main content
Vulnerability Database/CVE-2026-109672

CVE-2026-109672: Frappe ERPNext Authorization Bypass Flaw

CVE-2026-109672 is an authorization bypass vulnerability in Frappe ERPNext that allows authenticated users to access financial data beyond their role permissions. This post covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-109672 Overview

CVE-2026-109672 is a missing authorization vulnerability [CWE-862] in Frappe ERPNext, an open-source enterprise resource planning platform. Certain API endpoints fail to enforce role-based authorization checks before returning financial data. Authenticated users can query these endpoints and retrieve financial information beyond the scope their assigned role permits.

The flaw affects Frappe ERPNext versions prior to 15.118.0 and 16.x versions prior to 16.27.0. Exploitation requires valid authentication but no elevated privileges or user interaction, making the issue reachable by any low-privilege account inside the ERPNext tenant.

Critical Impact

Any authenticated ERPNext user can read financial data outside their authorized role scope, breaking segregation of duties and exposing sensitive accounting records.

Affected Products

  • Frappe ERPNext versions before 15.118.0
  • Frappe ERPNext 16.x versions before 16.27.0
  • Deployments exposing ERPNext endpoints to authenticated users across multiple roles

Discovery Timeline

  • 2026-10-12 - CVE-2026-109672 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-109672

Vulnerability Analysis

ERPNext exposes a large number of server-side endpoints that return accounting and financial records. The vulnerability stems from a subset of these endpoints that skip the permission layer Frappe normally enforces through its role and permission framework. When the authorization check is absent, the endpoint returns data based on query parameters alone, without validating whether the caller's role grants read access to the requested document types or fields.

The result is a horizontal and vertical privilege boundary failure. A user holding a limited role, for example a sales or support role, can issue requests that return general ledger entries, invoices, payment data, or related financial documents reserved for finance or accounting roles. The disclosure is confined to confidentiality; the CVSS v4.0 vector reports no impact on integrity or availability.

Root Cause

The root cause is a missing authorization check on specific endpoints that query financial doctypes. Frappe's standard pattern requires each endpoint to validate the caller against the permission matrix for the target doctype. The affected endpoints bypass this validation and reach the database layer directly. See the GitHub Security Advisory GHSA-rgrq-243c-c4g6 for the maintainers' description of the fix.

Attack Vector

The attack vector is network-based and authenticated. An attacker obtains a valid ERPNext session, either by compromising a low-privilege account or by using legitimate limited access. The attacker then issues HTTP requests to the vulnerable endpoints with crafted parameters that reference financial documents or filters. Because authorization is not enforced, the server returns the requested records regardless of the caller's role.

No exploit code is required beyond standard API usage against the vulnerable endpoints. Public proof-of-concept code is not currently listed in the enriched data. Refer to the VulnCheck advisory for additional context.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-109672

Indicators of Compromise

  • Repeated authenticated API calls to financial-record endpoints originating from accounts whose role profile does not include finance or accounting permissions.
  • Unusual spikes in /api/method or /api/resource calls targeting doctypes such as GL Entry, Sales Invoice, Purchase Invoice, or Payment Entry from non-finance users.
  • Session activity that enumerates financial doctype listings outside the user's normal workflow.

Detection Strategies

  • Correlate ERPNext application logs with role assignments to flag reads of financial doctypes by users lacking matching permissions.
  • Baseline per-role API usage and alert on deviations where low-privilege roles access financial endpoints.
  • Inspect reverse proxy or web server access logs for high-volume GET requests to Frappe API routes referencing financial doctypes.

Monitoring Recommendations

  • Forward ERPNext audit logs and web access logs to a centralized analytics platform for cross-user correlation.
  • Enable Frappe's built-in activity logging on financial doctypes and retain logs long enough to support incident review.
  • Monitor outbound data volumes from the ERPNext host for signs of bulk extraction following suspicious API activity.

How to Mitigate CVE-2026-109672

Immediate Actions Required

  • Upgrade ERPNext to version 15.118.0 or later on the 15.x branch, or 16.27.0 or later on the 16.x branch.
  • Audit role profiles and remove unnecessary access to API endpoints and financial doctypes for non-finance users.
  • Review recent application logs for unauthorized reads of financial doctypes by low-privilege accounts.

Patch Information

The Frappe maintainers released fixes in ERPNext 15.118.0 and 16.27.0. The patched versions add the missing authorization checks to the affected endpoints so that requests are validated against the caller's role permissions before data is returned. Patch details are published in the GitHub Security Advisory GHSA-rgrq-243c-c4g6.

Workarounds

  • Restrict network access to the ERPNext API to trusted internal networks or VPN users while patching is scheduled.
  • Rotate credentials for low-privilege accounts suspected of misuse and enforce multi-factor authentication on all ERPNext users.
  • Temporarily tighten role permissions and remove API access from roles that do not require it until the upgrade is applied.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.