Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged ERPNext user
-
ExploitCall endpoint lacking permission check
-
ExecutionDeactivate master records beyond role
-
ImpactDisrupt business data integrity
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated ERPNext account with low privileges (PR:L) and network access to the application; the attacker directly invokes specific endpoints that fail to enforce role-based permission checks, allowing deactivation of master records outside their assigned role. Exploitation is limited by the need for working credentials on the target instance - it is not reachable by fully unauthenticated attackers - and is scoped to integrity of master data (deactivation), with no path to data disclosure or service outage. Affects default configurations of ERPNext versions before 15.108.0 and 16.x before 16.18.0; patched instances are not exposed. |
| Impact | This is a moderate-severity authorization flaw (CWE-862), not a critical priority. The CVSS 4.0 vector (AV:N/AC:L/PR:L/UI:N) indicates network-reachable, low-complexity exploitation, but it requires an already-authenticated low-privileged account (PR:L), which meaningfully narrows the attacker population to insiders or anyone who has obtained valid low-tier credentials. Impact is constrained: only VI:L (low integrity) is set, with VC:N and VA:N, reflecting that the attacker can deactivate master records but cannot read sensitive data or cause outages - consistent with the 5.3 Medium base score. No EPSS score, CISA KEV listing, or public POC was provided in the intelligence, so there is no signal of active or widespread exploitation; this reads as a real-but-contained privilege/integrity issue rather than an urgent emergency. One data caveat: the input Tags label this 'Authentication Bypass,' which conflicts with the description and CWE-862 - this is a missing-authorization (privilege) flaw affecting already-authenticated users, not an authentication bypass; verify against the Frappe GHSA advisory before categorizing. |
| Exploit ScenarioDerived | A disgruntled employee or an attacker who has phished a standard low-privileged ERPNext user account logs in and invokes the affected endpoints directly, bypassing the role-based permission checks that the UI would normally enforce. Using this access they deactivate master records (such as customers, suppliers, or item masters) they are not authorized to modify, disrupting business operations. No public exploit identified at time of analysis, and low attack complexity means scripting the endpoint calls would be straightforward for someone with a valid session. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Authenticated users holding only low-privilege roles in Frappe ERPNext can call specific endpoints that fail to enforce role-based permission checks, allowing them to deactivate master records outside their assigned permissions. The flaw affects ERPNext releases before 15.108.0 and 16.x before 16.18.0 and carries a moderate 5.3 severity, with impact confined to the integrity of master data - the assessed vector shows no confidentiality loss, no availability impact, and no scope change. No public exploit code has been identified at time of analysis, and there is no indication of confirmed active exploitation (not listed in CISA KEV).
RemediationAI
Apply the vendor fix by upgrading to ERPNext 15.108.0 (v15 branch) or 16.18.0 (v16 branch) or later; these are the exact patched versions named in the advisory, and no backport to earlier point releases is documented. Until the upgrade can be scheduled, reduce exposure by tightening role assignments so that no non-administrative role holds write or delete permissions on master doctypes (Item, Customer, Supplier, Warehouse, Company, and similar), and by auditing the ERPNext Role Permission Manager for grants that exceed least privilege. Where the business can tolerate it, restrict access to the affected REST/RPC surface with a reverse-proxy rule or API allow-list limited to trusted service accounts, and enable audit logging / notification on deactivation or submission-state changes to master records so misuse is detected quickly. Note the trade-offs: aggressive role tightening can break legitimate purchasing or stock workflows that rely on those roles, and proxy-level filtering of API paths may interfere with integrations, custom apps, or mobile clients, so any such control should be tested in a staging instance first. Patch status: Vendor-released patch: 15.108.0 and 16.18.0.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a CWE-862 Missing Authorization weakness in the Frappe framework's ERPNext application. Frappe implements a DocType-level role permission model in which each record type carries role-based read/write/create/delete rules, and server-side methods are typically exposed through REST or RPC endpoints guarded by frappe.has_permission checks or the @frappe.whitelist decorator. The affected endpoints omitted or incorrectly applied those checks, so any authenticated session - even one whose assigned role has no authority over the doctype in question - could reach the underlying logic and flip master records into an inactive state. This is properly characterized as broken access control rather than a true authentication bypass; the reporting tags list 'Authentication Bypass', but the vulnerable code path still requires a valid login, which is why the assessed vector is PR:L (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) and the 5.3 CVSS 4.0 vector records VI:L with VC:N and VA:N. Because the affected component is an ERP master-data store shared across purchasing, inventory, and accounting workflows, unauthorized deactivation is a data-integrity and business-process risk rather than a path to code execution or data exfiltration.
Know when Erpnext gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Network-reachable endpoint (AV:N) with low complexity (AC:L) but requires an authenticated low-privileged account (PR:L); only limited integrity impact from deactivating records, so C:N/I:L/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
Frappe ERPNext before 15.108.0 and 16.x before 16.18.0 contains a missing authorization vulnerability in certain endpoints that fail to enforce proper permission checks. Authenticated low-privileged users can call these endpoints to deactivate master records, modifying data beyond their permitted role.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Stored cross-site scripting leading to code execution in Frappe Framework 15.89.0 (and the ERPNext application built on
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
Authenticated SQL injection in Frappe ERPNext through 15.89.0 allows low-privilege users to extract arbitrary database c
SQL injection in Frappe ERPNext through 15.89.0 lets an authenticated attacker with a valid session and access to the Pa
Authenticated attackers with permission to create or modify Print Format documents in Frappe ERPNext through 15.89.0 can
Authenticated server-side template injection in Frappe ERPNext through 15.89.0 lets a user who can create or modify an A
Authenticated server-side template injection in Frappe ERPNext through 15.89.0 allows users with privileges to configure
An SQL injection vulnerability exists in the frappe.desk.reportview.get functionality of ERPNext 11.1.38. Rated high sev
Frappe Framework ERPNext 13.4.0 contains a sandbox escape vulnerability in RestrictedPython that allows authenticated us
EUVD-2026-98056
GHSA-5grv-ghjx-fpqc
NVD
CVE.org
EPSS
Exploit-DB