Frappe ERPNext authorization bypass in Purchase Order close endpoint
Affects ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0 for users with Purchase Order write access. Fixed in 15.121.4 and 16.36.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 15.121.4, 16.36.0
- Who is exposed
- Specific setups only
Summary
Frappe ERPNext, the open-source business management software, has a missing authorization flaw in its Purchase Order close and reopen endpoint, which checks document-type write permission but not per-document User Permissions. An attacker with a valid low-privilege account and Purchase Order write access can remotely send crafted requests to change the status of another company's Purchase Order.
Written by a model
Original description
Frappe ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in the Buying module: the endpoint that closes and reopens Purchase Orders checks only document-type write permission, not per-document User Permissions. Authenticated users with Purchase Order write access can send crafted requests naming another company's Purchase Order to change its status.
Who should check
Teams running Frappe ERPNext 5.0.0 before 15.121.4 or 16.x before 16.36.0, especially those with multi-company setups using User Permissions in the Buying module.
“Frappe ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0”
What to do
Check whether your setup matches what the bug needs.
Affects ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0. Attacker needs Purchase Order write access; the endpoint checks only document-type write permission.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-134381 (Frappe ERPNext 5.0.0 before 15.121.4 Missing Authorization in Purchase Order Close 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-134381 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 5.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):
- Affects ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0. (source: https://www.vulncheck.com/advisories/frappe-erpnext-5.0.0-before-15.121.4-missing-authorization-in-purchase-order-close-endpoint)
- Attacker needs Purchase Order write access; the endpoint checks only document-type write permission. (source: https://www.vulncheck.com/advisories/frappe-erpnext-5.0.0-before-15.121.4-missing-authorization-in-purchase-order-close-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-134381 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134381 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-mmcf-jq27-crrp
- https://www.vulncheck.com/advisories/frappe-erpnext-5.0.0-before-15.121.4-missing-authorization-in-purchase-order-close-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-134381
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-134381"}.Affected versions
- frappe erpnextFrom 5.0.0 · fixed in 15.121.4
- frappe erpnextFrom 16.0.0 · fixed in 16.36.0
cve.now Index
- 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
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · frappe/erpnext · Advisory GHSA-mmcf-jq27-crrp |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134381 |
| Record | NVD · CVE-2026-134381 |
| Other links 1 | |
| Link | vulncheck.com · advisories/frappe-erpnext-5.0.0-before-15.121.4-missing-authorization-in-purchase-order-close-endpoint |
Questions about CVE-2026-134381
Is CVE-2026-134381 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 Purchase Order write access can close or reopen Purchase Orders that belong to other companies or fall outside their User Permissions, changing their status. The Purchase Order close endpoint checks only document-type write permission and does not enforce User Permissions.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134381?
erpnext: from 5.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 5.0.0 before 15.121.4 and 16.x before 16.36.0 are affected, provided users hold Purchase Order write access. To check a installation, compare the installed ERPNext version against these ranges, and review which users hold Purchase Order write permission and any User Permissions restrictions.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134381?
Upgrade ERPNext to 15.121.4 or 16.36.0, depending on the release line in use. The advisory does not name vendor patch identifiers, so the fixed versions are the upgrade targets.
Source: vulncheck.com, github.com
Related
- CVE-2026-134389Frappe ERPNext 6.18.0 before 15.124.0 Unauthorized Document Access via Payment Requests
- CVE-2026-134372Frappe ERPNext 4.3.0 before 15.121.6 SQL Injection in Selling and Buying Modules
- CVE-2026-134393Frappe ERPNext 10.1.41 before 15.122.0 Missing Authorization in Manufacturing BOM Replacement
- CVE-2026-134378Frappe ERPNext 12.7.0 before 15.124.0 Information Disclosure via Public Supplier E-Invoice Files
- CVE-2026-134373Frappe ERPNext 14.0.0 before 15.121.0 Missing Authorization in Bulk Transaction Retry
- CVE-2026-134374Frappe ERPNext 15.0.0 before 15.124.0 Missing Authorization in Assets Depreciation Endpoints
No corrections so far. Something wrong on this page? Report an error.