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

CVE-2026-108373: ERPNext Authorization Bypass Vulnerability

CVE-2026-108373 is an authorization bypass flaw in ERPNext that allows authenticated users to access financial data beyond their permitted roles. This post explains its impact, affected versions, and mitigation steps.

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-108373 Overview

CVE-2026-108373 is a missing authorization vulnerability [CWE-862] in ERPNext, the open source Enterprise Resource Planning (ERP) platform built on Frappe. The flaw resides in the Sales Person-wise Transaction Summary report. Affected endpoints fail to apply the requesting user's document permission match conditions when assembling the underlying query. A role-limited authenticated user can therefore retrieve financial transaction rows that fall outside their permitted scope. Maintainers resolved the issue in ERPNext versions 15.118.0 and 16.27.0.

Critical Impact

Authenticated users with limited roles can read financial transaction data belonging to other sales persons, companies, territories, or customers that their permissions should restrict.

Affected Products

  • ERPNext versions prior to 15.118.0 (15.x branch)
  • ERPNext versions prior to 16.27.0 (16.x branch)
  • Deployments exposing the Sales Person-wise Transaction Summary report to role-limited users

Discovery Timeline

  • 2026-10-16 - CVE-2026-108373 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-108373

Vulnerability Analysis

The Sales Person-wise Transaction Summary report in ERPNext constructs a database query against sales transaction doctypes such as Sales Order, Delivery Note, and Sales Invoice. The reporting function forwards the raw user-supplied filters dictionary directly into Frappe's get_query helper. That dictionary contains report-specific keys (for example doc_type, sales_person, item_group) that are not valid document fields on the queried doctype.

Because get_query cannot map those keys to document fields, the permission match conditions tied to the requesting user's role are not applied as expected. The query executes against the full transaction table, returning financial rows the caller should not see. The confidentiality impact is high; integrity and availability are not affected.

Root Cause

The root cause is a Missing Authorization check [CWE-862] in the report controller sales_person_wise_transaction_summary.py. The function conflates report filter parameters with document field filters when invoking frappe.get_query, which prevents Frappe's permission framework from attaching the user's User Permission match conditions to the SQL query.

Attack Vector

An authenticated user with any role that grants access to the Sales Person-wise Transaction Summary report can issue a crafted request to the report endpoint over the network. No user interaction is required, and attack complexity is low. The attacker reads financial data for sales persons, territories, or companies that their User Permissions were intended to restrict.

python
# Patch excerpt: sales_person_wise_transaction_summary.py
# Only pass valid document-field filters to get_query; report-specific keys such as
# doc_type / sales_person / item_group are handled separately below.
doc_filters = {"docstatus": 1}
for field in ["company", "customer", "territory"]:
    if filters.get(field):
        doc_filters[field] = filters.get(field)

if filters.get("from_date") and filters.get("to_date"):
    doc_filters[date_field] = ["between", [filters.get("from_date"), filters.get("to_date")]]
elif filters.get("from_date"):
    doc_filters[date_field] = [">=", filters.get("from_date")]
elif filters.get("to_date"):
    doc_filters[date_field] = ["<=", filters.get("to_date")]

query = (
    frappe.get_query(dt, filters=doc_filters, ignore_permissions=False)
    .join(dt_item)
    .on(dt.name == dt_item.parent)
    .join(st)
)

Source: GitHub Commit 24f0989. The patch constructs a sanitized doc_filters dictionary containing only valid document fields before calling frappe.get_query with ignore_permissions=False, restoring the user's permission match conditions.

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-108373

Indicators of Compromise

  • Requests to the ERPNext report endpoint api/method/frappe.desk.query_report.run with report_name=Sales Person-wise Transaction Summary issued by low-privilege users.
  • Report executions returning rows containing sales persons, companies, or territories outside the caller's assigned User Permissions.
  • Unusual report export or download activity by role-limited accounts.

Detection Strategies

  • Audit ERPNext activity logs for Sales Person-wise Transaction Summary executions and correlate the result set with the executing user's User Permissions.
  • Review web server access logs for repeated calls to query_report.run from the same user with varied filter parameters indicative of data enumeration.
  • Compare installed ERPNext versions against 15.118.0 and 16.27.0 to identify vulnerable instances across the estate.

Monitoring Recommendations

  • Enable Frappe audit logging and ship logs to a central analytics platform for retention and query.
  • Alert on report runs that return abnormally large result sets for accounts with narrow User Permission scopes.
  • Baseline normal report usage per role and flag deviations in request frequency or exported row counts.

How to Mitigate CVE-2026-108373

Immediate Actions Required

  • Upgrade ERPNext to version 15.118.0 or 16.27.0, matching the branch currently in production.
  • Inventory users who hold roles permitting access to the Sales Person-wise Transaction Summary report and review their recent activity.
  • Validate User Permission assignments for Sales Person, Company, and Territory to ensure least privilege.

Patch Information

The fix is tracked in GitHub Security Advisory GHSA-rgrq-243c-c4g6 and delivered through commits 202f522 and 24f0989. Patched builds are published as ERPNext v15.118.0 and ERPNext v16.27.0.

Workarounds

  • Temporarily revoke the role permission that allows low-privilege users to execute the Sales Person-wise Transaction Summary report until the patch is deployed.
  • Restrict network access to the ERPNext report endpoints to trusted administrator roles via reverse proxy or application firewall rules.
  • Monitor and rate-limit calls to frappe.desk.query_report.run targeting the affected report name.
bash
# Upgrade ERPNext using the bench CLI
bench switch-to-branch version-15 erpnext --upgrade   # for 15.x deployments
bench update --reset
bench --site <site-name> migrate

# Verify installed version matches a patched release
bench version | grep erpnext
# Expected: erpnext 15.118.0  (or 16.27.0)

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.