Frappe ERPNext unauthorized private file read in Accounts module
Affects ERPNext 12.0.0 before 15.121.4 and 16.x before 16.36.0, where private import-format files can be read by authenticated users. Fixed in 15.121.4 and 16.36.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 15.121.4, 16.36.0
- Who is exposed
- Specific setups only
Summary
Written by a model
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 endpoint that returns the parsed content of private import-format files without checking permission on the requested records. Authenticated attackers, including portal users or users without roles, can send crafted requests naming records outside their permitted scope to read those private files.
Who should check
Teams running Frappe ERPNext 12.0.0 before 15.121.4 or 16.x before 16.36.0, especially those with portal users or users without roles
“Frappe ERPNext 12.0.0 before 15.121.4 and 16.x before 16.36.0”
What to do
Check whether your setup matches what the bug needs.
Affects ERPNext 12.0.0 before 15.121.4, and 16.x before 16.36.0 Exposure is limited to files in a specific import formatUpgrade to a fixed version: 15.121.4, 16.36.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134430 (Frappe ERPNext 12.0.0 before 15.121.4 Unauthorized Private File Read in Accounts Module), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134430 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 12.0.0, fixed in 15.121.4
- frappe erpnext: from 16.0.0, fixed in 16.36.0
Fixed versions: 15.121.4, 16.36.0.
Conditions (all must be true for the bug to be hit):
- Affects ERPNext 12.0.0 before 15.121.4, and 16.x before 16.36.0 (source: https://www.vulncheck.com/advisories/frappe-erpnext-12.0.0-before-15.121.4-unauthorized-private-file-read-in-accounts-module)
- Exposure is limited to files in a specific import format (source: https://github.com/frappe/erpnext/security/advisories/GHSA-g966-fmq7-gp99)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134430 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134430 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/frappe/erpnext/security/advisories/GHSA-g966-fmq7-gp99
- https://www.vulncheck.com/advisories/frappe-erpnext-12.0.0-before-15.121.4-unauthorized-private-file-read-in-accounts-module
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134430
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134430"}.Affected versions
- frappe erpnextFrom 12.0.0 · fixed in 15.121.4
- frappe erpnextFrom 16.0.0 · fixed in 16.36.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 20 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · frappe/erpnext · Advisory GHSA-g966-fmq7-gp99 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134430 |
| Record | NVD · CVE-2026-134430 |
| Other links 1 | |
| Link | vulncheck.com · advisories/frappe-erpnext-12.0.0-before-15.121.4-unauthorized-private-file-read-in-accounts-module |
Questions about CVE-2026-134430
Is CVE-2026-134430 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
An authenticated user, including portal users or users without roles, can read the parsed content of private import-format files by naming records outside their permitted scope. The read happens because the permission check on the requested records is missing.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134430?
erpnext: from 12.0.0 before 15.121.4. erpnext: from 16.0.0 before 16.36.0.
Source: cve.now feed data
Am I affected, and how do I check?
ERPNext 12.0.0 before 15.121.4 and 16.x before 16.36.0 are affected. Exposure is limited to files in a specific import format, so compare your installed ERPNext version against these ranges.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134430?
Upgrade to ERPNext 15.121.4 or 16.36.0, the fixed versions for each affected line.
Source: vulncheck.com, github.com
Related
- CVE-2026-134389Frappe ERPNext 6.18.0 before 15.124.0 Unauthorized Document Access via Payment Requests
- CVE-2026-134372Frappe ERPNext 4.3.0 before 15.121.6 SQL Injection in Selling and Buying Modules
- CVE-2026-134378Frappe ERPNext 12.7.0 before 15.124.0 Information Disclosure via Public Supplier E-Invoice Files
- CVE-2026-134373Frappe ERPNext 14.0.0 before 15.121.0 Missing Authorization in Bulk Transaction Retry
- CVE-2026-134374Frappe ERPNext 15.0.0 before 15.124.0 Missing Authorization in Assets Depreciation Endpoints
- CVE-2026-134375Frappe ERPNext 13.0.0 before 15.124.0 Missing Authorization in Accounts Payment Entries
No corrections so far. Something wrong on this page? Report an error.