Skip to main content
Menu
CVEs

Frappe ERPNext missing authorization exposes bank statement files

Affects ERPNext 13.0.0 before 15.121.4 and 16.x before 16.36.0 through the bank statement import endpoint. Fixed in 15.121.4 and 16.36.0.

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

8.3HighCNA
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 13.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 uploaded bank statement file content without checking record-level permissions. Authenticated attackers, including portal users or users with no assigned roles, can send crafted requests naming records outside their scope to read full statement file contents.

Who should check

Teams running ERPNext 13.0.0 up to 15.121.4, or 16.x before 16.36.0, with the Accounts module bank statement import endpoint, including portal users

“Frappe ERPNext 13.0.0 before 15.121.4 and 16.x before 16.36.0”

vulncheck.com

What to do

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

    ERPNext versions 13.0.0 before 15.121.4, or 16.x before 16.36.0
  2. Upgrade 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-134417 (ERPNext 13.0.0 before 15.121.4 Missing Authorization in Bank Statement Import Endpoint), 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-134417 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 13.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):
- ERPNext versions 13.0.0 before 15.121.4, or 16.x before 16.36.0 (source: https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint)
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-134417 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134417 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-m9wx-ccvr-729q
- https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint
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-134417
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-134417"}.

Affected versions

cve.now Index

16Pof 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
  • Severity8.3/10CVSS 8.3
  • 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

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

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · frappe/erpnext · Advisory GHSA-m9wx-ccvr-729q
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134417
RecordNVD · CVE-2026-134417
Other links 1
Linkvulncheck.com · advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint

Questions about CVE-2026-134417

Is CVE-2026-134417 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?

The bank statement import endpoint does not check authorization properly, so an authenticated user can read the full contents of uploaded bank statement files for records outside their permitted scope.

Source: vulncheck.com

Which versions are affected by CVE-2026-134417?

erpnext: from 13.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 13.0.0 before 15.121.4, and 16.x before 16.36.0. To check a version, look at the installed ERPNext version reported for the erpnext app on the site.

Source: vulncheck.com

How do I fix CVE-2026-134417?

Upgrade to ERPNext 15.121.4 on the 15.x line or 16.36.0 on the 16.x line, which are the fixed versions for this vulnerability.

Source: vulncheck.com

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