Frappe ERPNext unauthorized document access via payment requests
Affects ERPNext 6.18.0 before 15.124.0 and 16.x before 16.52.0, where users with the Accounts User role can read documents they lack permission for. Fixed in 15.124.0 and 16.52.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 15.124.0, 16.52.0
- Who is exposed
- Specific setups only
Summary
Frappe ERPNext, a business management application, has a missing authorization flaw in its Payment Requests feature. A remote attacker with a low-privilege Accounts User login can create a Payment Request that references another company's document, then have that document's content emailed to an address of their choosing, exposing data they should not be able to read.
Written by a model
Original description
Frappe ERPNext 6.18.0 before 15.124.0 and 16.x before 16.52.0 contains a missing authorization vulnerability in Payment Requests that lets authenticated Accounts User role holders read source documents they lack permission to access. Attackers can create a Payment Request through the generic record interface that references another company's document, then email its loaded content to an address they choose.
Who should check
Teams running Frappe ERPNext 6.18.0 through 15.x before 15.124.0, or 16.x before 16.52.0, where users hold the Accounts User role
“Frappe ERPNext 6.18.0 before 15.124.0 and 16.x before 16.52.0”
What to do
Check whether your setup matches what the bug needs.
Frappe ERPNext 6.18.0 before 15.124.0, or 16.x before 16.52.0 Attacker must hold the Accounts User roleUpgrade to a fixed version: 15.124.0, 16.52.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-134389 (Frappe ERPNext 6.18.0 before 15.124.0 Unauthorized Document Access via Payment Requests), 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-134389 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 6.18.0, fixed in 15.124.0
- frappe erpnext: from 16.0.0, fixed in 16.52.0
Fixed versions: 15.124.0, 16.52.0.
Conditions (all must be true for the bug to be hit):
- Frappe ERPNext 6.18.0 before 15.124.0, or 16.x before 16.52.0 (source: https://www.vulncheck.com/advisories/frappe-erpnext-6.18.0-before-15.124.0-unauthorized-document-access-via-payment-requests)
- Attacker must hold the Accounts User role (source: https://www.vulncheck.com/advisories/frappe-erpnext-6.18.0-before-15.124.0-unauthorized-document-access-via-payment-requests)
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-134389 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134389 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-64h3-xccr-q5jr
- https://www.vulncheck.com/advisories/frappe-erpnext-6.18.0-before-15.124.0-unauthorized-document-access-via-payment-requests
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-134389
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-134389"}.Affected versions
- frappe erpnextFrom 6.18.0 · fixed in 15.124.0
- frappe erpnextFrom 16.0.0 · fixed in 16.52.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
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 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-64h3-xccr-q5jr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134389 |
| Record | NVD · CVE-2026-134389 |
| Other links 1 | |
| Link | vulncheck.com · advisories/frappe-erpnext-6.18.0-before-15.124.0-unauthorized-document-access-via-payment-requests |
Questions about CVE-2026-134389
Is CVE-2026-134389 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?
A missing authorization check lets a logged-in user with the Accounts User role read the content of documents they cannot normally access. The same flaw also lets them create Payment Requests against documents belonging to other companies.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134389?
erpnext: from 6.18.0 before 15.124.0. erpnext: from 16.0.0 before 16.52.0.
Source: cve.now feed data
Am I affected, and how do I check?
ERPNext 6.18.0 before 15.124.0 and 16.x before 16.52.0 are affected. To check a setup, look at the installed ERPNext version and see whether any accounts users hold the Accounts User role.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134389?
Upgrade ERPNext to 15.124.0 on the 15.x line or to 16.52.0 on the 16.x line.
Source: vulncheck.com, github.com
Related
- CVE-2026-134372Frappe ERPNext 4.3.0 before 15.121.6 SQL Injection in Selling and Buying Modules
- CVE-2026-134393Frappe ERPNext 10.1.41 before 15.122.0 Missing Authorization in Manufacturing BOM Replacement
- 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.