Skip to main content
Menu
CVEs

Frappe ERPNext unauthorized read of sales order items in selling module

Affects Frappe ERPNext 13.49.0 before 14.0.0, 14.17.2 before 15.124.0, and 16.x before 16.52.0, in the Selling module's Sales Order items. Fixed in 14.0.0, 15.124.0, and 16.52.0.

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

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

Summary

Written by a model

Frappe ERPNext 13.49.0 before 14.0.0, 14.17.2 before 15.124.0, and 16.x before 16.52.0 contains a missing authorization vulnerability in a Selling module endpoint that returns Sales Order line items without checking whether the caller may read the requested records. Authenticated attackers, including portal users or users with no assigned roles, can send crafted requests naming out-of-scope Sales Orders to read their line item data.

Who should check

Teams running Frappe ERPNext 13.49.0 through 15.123.x or 16.x before 16.52.0, including hosts with portal users or users with no assigned roles.

“Frappe ERPNext 13.49.0 before 14.0.0, 14.17.2 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.49.0 before 14.0.0, 14.17.2 before 15.124.0, and 16.x before 16.52.0.
  2. Upgrade to a fixed version: 14.0.0, 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-134400 (Frappe ERPNext 13.49.0 before 14.0.0 and 14.17.2 before 15.124.0 Missing Authorization in Selling Module Sales Order Items), 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-134400 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 13.49.0, fixed in 14.0.0
- frappe erpnext: from 14.17.2, fixed in 15.124.0
- frappe erpnext: from 16.0.0, fixed in 16.52.0
Fixed versions: 14.0.0, 15.124.0, 16.52.0.
Conditions (all must be true for the bug to be hit):
- Affected ERPNext versions: 13.49.0 before 14.0.0, 14.17.2 before 15.124.0, and 16.x before 16.52.0. (source: https://www.vulncheck.com/advisories/frappe-erpnext-13.49.0-before-14.0.0-and-14.17.2-before-15.124.0-missing-authorization-in-selling-module-sales-order-items)
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-134400 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134400 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-hfj8-f2p9-f2xf
- https://www.vulncheck.com/advisories/frappe-erpnext-13.49.0-before-14.0.0-and-14.17.2-before-15.124.0-missing-authorization-in-selling-module-sales-order-items
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-134400
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-134400"}.

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

Questions about CVE-2026-134400

Is CVE-2026-134400 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 Selling module does not enforce authorization on Sales Order items, so an authenticated user can read the line items of Sales Orders outside their permitted scope.

Source: vulncheck.com

Which versions are affected by CVE-2026-134400?

erpnext: from 13.49.0 before 14.0.0. erpnext: from 14.17.2 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.49.0 before 14.0.0, 14.17.2 before 15.124.0, and 16.x before 16.52.0 are affected. Check the installed ERPNext version against these ranges.

Source: vulncheck.com

How do I fix CVE-2026-134400?

Upgrade to 14.0.0 or later in the 13.49.0 line, 15.124.0 or later in the 14.17.2 line, or 16.52.0 or later in the 16.x line.

Source: vulncheck.com

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