Frappe ERPNext up to 15.121.3/16.35.x Accounts improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00+ |
Summary
A vulnerability has been found in Frappe ERPNext up to 15.121.3/16.35.x and classified as problematic. Impacted is an unknown function of the component Accounts Module. The manipulation leads to improper authorization. This vulnerability is documented as CVE-2026-134387. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Frappe ERPNext up to 15.121.3/16.35.x and classified as problematic. This issue affects an unknown part of the component Accounts Module. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality. The summary by CVE is:
Frappe ERPNext 12.0.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module dashboard chart source that returns account balance history without checking chart or account permissions. Authenticated attackers, including portal users or users with no roles, can send crafted requests naming any account to read general ledger balance history of any company.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-134387 since 11/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 15.121.4 or 16.36.0 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.6VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.0
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/21/2026 Advisory disclosed11/21/2026 CVE reserved
11/21/2026 VulDB entry created
11/21/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: VulnCheck
CVE: CVE-2026-134387 (🔒)
GCVE (CVE): GCVE-0-2026-134387
GCVE (VulDB): GCVE-100-441941
Entry
Created: 11/21/2026 18:18Changes: 11/21/2026 18:18 (76)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.