Frappe ERPNext up to 15.121.9/16.49.9 Stock improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as problematic, has been found in Frappe ERPNext up to 15.121.9/16.49.9. Affected by this issue is some unknown functionality of the component Stock Module. Performing a manipulation results in improper authorization. This vulnerability is identified as CVE-2026-134410. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Frappe ERPNext up to 15.121.9/16.49.9. This affects an unknown functionality of the component Stock Module. The manipulation 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. The summary by CVE is:
Frappe ERPNext 15.0.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in a Stock module endpoint that returns Serial No and Batch ledger entries without checking whether the caller may read the requested records. Authenticated attackers, including portal users or users without roles, can send crafted requests naming out-of-scope records to obtain item codes, quantities, warehouses, batch and serial numbers.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-134410 since 11/21/2026. The exploitability is told to be easy. It is possible to initiate the attack 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.122.0 or 16.50.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
- 15.121.4
- 15.121.5
- 15.121.6
- 15.121.7
- 15.121.8
- 15.121.9
- 16.49.0
- 16.49.1
- 16.49.2
- 16.49.3
- 16.49.4
- 16.49.5
- 16.49.6
- 16.49.7
- 16.49.8
- 16.49.9
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.122.0/16.50.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-134410 (🔒)
GCVE (CVE): GCVE-0-2026-134410
GCVE (VulDB): GCVE-100-441981
Entry
Created: 11/21/2026 18:30Changes: 11/21/2026 18:30 (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.