Skip to content

CVE-2026-130787

ERPNext financial reporting endpoints allow unauthorised data access (CVE-2026-130787)

High 8.3 Vendor: Frappe / ERPNext Published

ERPNext 16.0.0 up to but not including 16.35.0, and releases before 15.121.3, have a missing authorization flaw in financial reporting endpoints. A low-privileged authenticated user can read other companies' tax and payment data. Update to 16.35.0 or 15.121.3.

What happened

Frappe ERPNext contains a missing authorization vulnerability in its financial reporting endpoints. An attacker with a low-privileged authenticated account can send crafted requests over the network to those endpoints and generate reports outside the scope permitted to that account. No user interaction is needed beyond the attacker's own authenticated access.

The data exposed includes other companies' tax and payment information, personal and corporate identifiers, and financial totals. The CVSS 4.0 score is 8.3, rated high, with high confidentiality impact on the vulnerable system and on subsequent systems; integrity and availability are not affected.

The CVE record does not list exploitation in the wild or public disclosure.

Who is affected

ERPNext version 16.0.0 up to but not including 16.35.0 is affected, as are ERPNext releases before 15.121.3. Organisations that run ERPNext for financial reporting across more than one company face the greatest exposure, because a low-privileged user in one company can read another company's tax and payment data.

What to do now

  1. Upgrade affected installations. If you run the 16.x release line, update to ERPNext 16.35.0. If you are on the 15.x release line, update to ERPNext 15.121.3.
  2. Roll out the update before low-privileged users continue to have access to financial reporting endpoints.
  3. If you cannot update immediately, restrict low-privileged accounts from reaching financial reporting endpoints and monitor reporting activity for access outside their normal company scope.

The GitHub advisory does not list a workaround.

How to detect it

The GitHub advisory does not publish indicators of compromise. Until the update is applied, treat unexpected financial report generation by low-privileged accounts as suspicious, especially requests covering a company other than the account's assigned company.

Beyond the patch

Whether ERPNext is run in-house or through an implementation partner, this fix needs to reach every affected instance promptly. Spirity's Supply Chain Defense & Third-Party Risk service tracks which vendors' software you run and how quickly critical updates are applied, so a missing authorization fix such as this does not sit unpatched.

Affected and fixed versions

ProductAffectedFixed in
erpnext16.0.0 – < 16.35.016.35.0
15.121.3
erpnext– < 15.121.316.35.0
15.121.3

References

Sources: the CVE record (MITRE), NVD, CISA KEV and SSVC, ENISA EUVD, FIRST EPSS and the vendor's own advisory. Scores and dates are shown as those sources publish them.

Written with AI assistance from the sources above and checked automatically against them before publication.