Frappe ERPNext up to 15.121.3/16.35.x Payment Ledger get_linked_payments_for_doc company/doctype/docname improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.39+ |
Summary
A vulnerability categorized as problematic has been discovered in Frappe ERPNext up to 15.121.3/16.35.x. The affected element is the function get_linked_payments_for_doc of the component Payment Ledger. The manipulation of the argument company/doctype/docname results in improper authorization.
This vulnerability is identified as CVE-2026-124313. The attack can be executed remotely. There is not any exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Frappe ERPNext up to 15.121.3/16.35.x. It has been classified as problematic. Affected is the function get_linked_payments_for_doc of the component Payment Ledger. The manipulation of the argument company/doctype/docname with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. CVE summarizes:
Frappe ERPNext before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in the whitelisted get_linked_payments_for_doc method. Any authenticated user, including portal users, can supply arbitrary company, doctype, and docname values to read Payment Ledger Entry allocation data for other companies' invoices and vouchers.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-124313 since 11/07/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1548.002.
Upgrading to version 15.121.4 or 16.36.0 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 15.121.0
- 15.121.1
- 15.121.2
- 15.121.3
- 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
- 16.23
- 16.24
- 16.25
- 16.26
- 16.27
- 16.28
- 16.29
- 16.30
- 16.31
- 16.32
- 16.33
- 16.34
- 16.35
Website
- Product: https://github.com/frappe/erpnext/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (VulnCheck): 🔒
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: Improper authorizationCWE: CWE-285 / 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.121.4/16.36.0
Timeline
11/07/2026 Advisory disclosed11/07/2026 CVE reserved
11/07/2026 VulDB entry created
11/07/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: VulnCheck
CVE: CVE-2026-124313 (🔒)
GCVE (CVE): GCVE-0-2026-124313
GCVE (VulDB): GCVE-100-432636
Entry
Created: 11/07/2026 15:41Changes: 11/07/2026 15:41 (78)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.