CVE-2026-134389
ERPNext Payment Requests missing authorization exposes other companies' documents (CVE-2026-134389)
Frappe ERPNext 6.18.0 to before 15.124.0 and 16.x before 16.52.0 lets an authenticated Accounts User create a Payment Request referencing another company's document and email its content to a chosen address. No exploitation is recorded. Upgrade to the fixed releases.
What happened
CVE-2026-134389 is a missing authorization flaw, classified as CWE-862, in ERPNext's Payment Requests. An attacker with the Accounts User role can use the generic record interface to create a Payment Request that references a source document belonging to another company, then email the loaded content of that document to an email address they choose. The attack is network-based, requires only low privileges, and needs no victim interaction.
The CVSS 4.0 score is 8.4, high severity. The primary impact is confidentiality: an otherwise limited accounts role can be turned into a means of reading documents the user should not be able to open. There is no recorded exploitation or public disclosure in the CVE record.
Who is affected
ERPNext versions 6.18.0 through before 15.124.0 are affected, as are versions 16.0.0 through before 16.52.0. ERPNext is an open-source ERP platform used for finance, inventory, sales and purchasing, and Payment Requests are part of accounts workflows. Organisations running multiple companies in a single ERPNext instance, or with users holding the Accounts User role, should treat this as relevant. If your ERPNext version falls within these ranges, you are affected.
What to do now
- Upgrade ERPNext to the fixed release for your branch: 15.124.0 for installations on the 6.18–15.x line, or 16.52.0 for installations on the 16.x line.
- If you cannot patch immediately, review Accounts User role membership and monitor Payment Request creation and outbound email activity. No workaround is listed in the available advisory data.
- Treat any Payment Request created through the generic record interface that references a document outside the user's own company as suspicious.
How to detect it
No indicators of compromise are published. Based on the vulnerability mechanics, teams can review recently created Payment Requests for references to documents outside the creator's company and check email logs for Payment Request emails sent to unexpected recipients. Also trace unusual access to source documents by Accounts Users.
Beyond the patch
This missing-authorization flaw is a reminder that ERP authorisation models deserve the same testing as internet-facing applications. Implementation & Assessment Services can run a penetration test and hardening review against ERPNext instances and any customer or supplier-facing components to catch gaps like this before they are exploited. Because ERPNext is open-source software you deploy and patch yourself, track it in your software inventory with Supply Chain Defense & Third-Party Risk so the next patch cycle is visible and scheduled.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| erpnext | 6.18.0 – < 15.124.0 | 15.124.0 16.52.0 |
| erpnext | 16.0.0 – < 16.52.0 | 15.124.0 16.52.0 |