CVE-2026-72909: high-severity vulnerability in frappe erpnext
ERPNext: Broken Access Control on certain endpoints
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.5%
ERPNext is a free and open source Enterprise Resource Planning tool. Prior to 15.112.0 and 16.23.0, the ReceivablePayableReport prepare_conditions path in erpnext/accounts/report/accounts_receivable/accounts_receivable.py does not apply Customer and Supplier user permissions to the Payment Ledger Entry dynamic-link party field, allowing any authenticated user to read unauthorized cross-company financial data in Accounts Receivable and Accounts Payable reports. This issue is fixed in versions 15.112.0 and 16.23.0.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
frappe · erpnextRelated CVEs — frappe erpnext
In the same product, most dangerous first.
CVE-2026-65974CRITICALERPNext: Server-Side Template Injection leading to Remote Code ExecutionEPSS 1.0%CVE-2026-72911CRITICALERPNext: Possibility of server-side template injection due to missing validationEPSS 0.7%CVE-2026-72908MEDIUMERPNext: Possibility of SQL injection due to missing validationEPSS 0.5%CVE-2026-72910HIGHERPNext: Unauthorised modification of master data due to missing validationEPSS 0.5%CVE-2026-65822HIGHERPNext: SQL Injection in "Inactive Customers" report via unvalidated `doctype` filterEPSS 0.5%CVE-2026-72907MEDIUMERPNext: Broken Access Control on certain endpointEPSS 0.4%
References
https://github.com/frappe/erpnext/commit/b05abbc53b3655b02db17ba2e8165519f195c1c2https://github.com/frappe/erpnext/commit/c03a66a1bf48a53c42d01c9d936d9b22aa013e11https://github.com/frappe/erpnext/pull/55696https://github.com/frappe/erpnext/releases/tag/v15.112.0https://github.com/frappe/erpnext/releases/tag/v16.23.0https://github.com/frappe/erpnext/security/advisories/GHSA-p577-cxv9-h82f