Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-109643 Overview
CVE-2026-109643 is a missing authorization vulnerability [CWE-862] in Frappe ERPNext. Affected versions include ERPNext before 15.111.0 and 16.x before 16.22.0. Certain project-related endpoints fail to enforce permission checks before returning data. Authenticated low-privileged users can call these endpoints directly to read project records beyond their assigned role. The flaw exposes confidential project data without requiring additional privileges or user interaction. The issue is network-exploitable with low attack complexity and affects only confidentiality.
Critical Impact
Any authenticated ERPNext user can read project data that their role would otherwise block, enabling horizontal access to sensitive project information.
Affected Products
- Frappe ERPNext versions before 15.111.0
- Frappe ERPNext 16.x versions before 16.22.0
- Deployments exposing project module endpoints to authenticated users
Discovery Timeline
- 2026-10-12 - CVE-2026-109643 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-109643
Vulnerability Analysis
ERPNext organizes project data behind Frappe's role-based permission system. Specific project-related endpoints bypass that permission layer and return records directly from the database. An authenticated user holding a low-privileged role can invoke these endpoints and receive project data outside their permission scope. The exposure is limited to confidentiality — the endpoints do not enable modification or denial of service. However, project records often contain customer identifiers, financial estimates, internal task notes, and resource allocations that organizations expect to be restricted by role.
Root Cause
The vulnerable endpoints omit explicit permission checks that the Frappe framework normally enforces through has_permission calls or @frappe.whitelist guards. Server-side code assumes the caller is authorized because the user is authenticated. This maps directly to CWE-862 (Missing Authorization). The fix in 15.111.0 and 16.22.0 adds the missing permission enforcement before returning project data.
Attack Vector
Exploitation requires only a valid authenticated session with the lowest project-adjacent role. The attacker issues HTTP requests to the affected project endpoints using standard ERPNext API conventions. No social engineering, chained vulnerability, or elevated privilege is required. In multi-tenant or customer-portal deployments, this allows internal users or external collaborators to enumerate project data that belongs to other teams, departments, or customers.
No public proof-of-concept exploit code has been published for CVE-2026-109643. Technical details are available in the GitHub Security Advisory GHSA-q3vp-8w4j-x78w and the Vulncheck Advisory on Frappe ERPNext.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-109643
Indicators of Compromise
- Unusual volumes of requests from low-privileged user sessions to project-related ERPNext API endpoints
- Access to Project doctype records by users whose role profile does not include the Projects module
- Repeated enumeration patterns against sequential project names or identifiers in web server logs
Detection Strategies
- Review Frappe audit and access logs for authenticated users retrieving project records outside their assigned role scope
- Correlate HTTP request logs with ERPNext role assignments to flag mismatched access to project endpoints
- Alert on API clients that query project endpoints without previously accessing the Projects UI
Monitoring Recommendations
- Enable Frappe's request logging and ship logs to a centralized SIEM for retention and correlation
- Baseline normal project endpoint usage per role, then alert on deviations
- Monitor for new or unexpected API tokens issued to low-privileged accounts
How to Mitigate CVE-2026-109643
Immediate Actions Required
- Upgrade ERPNext to 15.111.0 or later on the 15.x branch
- Upgrade ERPNext to 16.22.0 or later on the 16.x branch
- Audit existing role permissions on the Project, Task, and related doctypes and remove unnecessary access
- Rotate API keys and secrets for accounts suspected of unauthorized project data access
Patch Information
Frappe fixed the missing authorization checks in ERPNext 15.111.0 and 16.22.0. The patched releases add explicit permission enforcement in the affected project endpoints. Refer to the GitHub Security Advisory GHSA-q3vp-8w4j-x78w for upgrade guidance and commit references.
Workarounds
- Restrict network access to the ERPNext instance so only trusted users can reach the API
- Reduce the number of accounts holding any project-adjacent role until patching is complete
- Place a reverse proxy or WAF rule in front of ERPNext to log and rate-limit calls to project endpoints
# Upgrade ERPNext using the bench CLI
bench update --reset
bench --site <your-site> migrate
bench version # confirm erpnext >= 15.111.0 or >= 16.22.0
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

