Frappe ERPNext up to 15.111.x/16.22.x ReceivablePayableReport accounts_receivable.py prepare_conditions permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 1.83 |
Summary
A vulnerability, which was classified as problematic, has been found in Frappe ERPNext up to 15.111.x/16.22.x. This impacts the function prepare_conditions of the file erpnext/accounts/report/accounts_receivable/accounts_receivable.py of the component ReceivablePayableReport. This manipulation causes permission.
This vulnerability appears as CVE-2026-72909. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability has been found in Frappe ERPNext up to 15.111.x/16.22.x and classified as problematic. Affected by this vulnerability is the function prepare_conditions of the file erpnext/accounts/report/accounts_receivable/accounts_receivable.py of the component ReceivablePayableReport. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-72909 since 08/10/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Upgrading to version 15.112.0 or 16.23.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 15.111
- 16.0
- 16.1
- 16.2
- 16.3
- 16.4
- 16.5
- 16.6
- 16.7
- 16.8
- 16.9
- 16.10
- 16.11
- 16.12
- 16.13
- 16.14
- 16.15
- 16.16
- 16.17
- 16.18
- 16.19
- 16.20
- 16.21
- 16.22
Website
- Product: https://github.com/frappe/erpnext/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: ERPNext 15.112.0/16.23.0
Timeline
08/10/2026 Advisory disclosed08/10/2026 CVE reserved
08/10/2026 VulDB entry created
08/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-72909 (🔒)
GCVE (CVE): GCVE-0-2026-72909
GCVE (VulDB): GCVE-100-387913
Entry
Created: 08/10/2026 23:26Changes: 08/10/2026 23:26 (57)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.