Skip to main content
Menu
CVEs

Frappe ERPNext authorization bypass in accounts payment entries

Affects ERPNext 13.0.0 before 15.124.0 and 16.x before 16.52.0 for users with an Accounts role whose user permissions restrict Payment Entries, such as by Cost Center. Fixed in 15.124.0 and 16.52.0.

CVE-2026-134375Published November 21, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 15.124.0, 16.52.0
Who is exposed
Specific setups only

Summary

Frappe ERPNext has a missing authorization flaw in its Accounts Payment Entries endpoint. A remote attacker with a low-privilege login and an Accounts role can view metadata of Payment Entries that their user permissions, such as Cost Center restrictions, should hide.

Written by a model

Original description

Frappe ERPNext 13.0.0 before 15.124.0 and 16.x before 16.52.0 contains an incorrect authorization vulnerability in an Accounts module endpoint that returns Payment Entries for a readable bank record without checking read permission on each Payment Entry. Authenticated users with an Accounts role can request a readable record to obtain metadata of Payment Entries excluded by their user permissions, such as Cost Center restrictions.

Who should check

Teams running Frappe ERPNext 13.0.0 up to 15.124.0 or 16.x before 16.52.0, where users with the Accounts role are restricted by user permissions such as Cost Center.

“Frappe ERPNext 13.0.0 before 15.124.0 and 16.x before 16.52.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affected ERPNext versions: 13.0.0 up to before 15.124.0, and 16.x before 16.52.0. Attacker must hold an Accounts role and be restricted by user permissions such as Cost Center restrictions.
  2. Upgrade 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-134375 (Frappe ERPNext 13.0.0 before 15.124.0 Missing Authorization in Accounts Payment Entries), 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-134375 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 13.0.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):
- Affected ERPNext versions: 13.0.0 up to before 15.124.0, and 16.x before 16.52.0. (source: https://www.vulncheck.com/advisories/frappe-erpnext-13.0.0-before-15.124.0-missing-authorization-in-accounts-payment-entries)
- Attacker must hold an Accounts role and be restricted by user permissions such as Cost Center restrictions. (source: https://www.vulncheck.com/advisories/frappe-erpnext-13.0.0-before-15.124.0-missing-authorization-in-accounts-payment-entries)
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-134375 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134375 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-45p2-2pp7-f8w2
- https://www.vulncheck.com/advisories/frappe-erpnext-13.0.0-before-15.124.0-missing-authorization-in-accounts-payment-entries
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-134375
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-134375"}.

Affected versions

cve.now Index

13Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · frappe/erpnext · Advisory GHSA-45p2-2pp7-f8w2
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134375
RecordNVD · CVE-2026-134375
Other links 1
Linkvulncheck.com · advisories/frappe-erpnext-13.0.0-before-15.124.0-missing-authorization-in-accounts-payment-entries

Questions about CVE-2026-134375

Is CVE-2026-134375 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 with an Accounts role can request a Payment Entry record and read its metadata even when their user permissions, such as Cost Center restrictions, exclude that record. The access stays within the same company.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134375?

erpnext: from 13.0.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 13.0.0 before 15.124.0 and 16.x before 16.52.0 are in the affected range. Check the installed ERPNext version against these ranges, and note that the issue concerns Accounts-role users whose permissions restrict Payment Entries.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134375?

Upgrade to ERPNext 15.124.0 or later in the 15.x line, or to 16.52.0 or later in the 16.x line.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.