Frappe ERPNext CVE-2026-109631

Exploitation requires a valid authenticated ERPNext session with at least low privileges (PR:L) - it is not exploitable by anonymous/unauthenticated users. The attacker must reach one of the specific endpoints that lack input validation and submit crafted input that is concatenated into a database query; the exact endpoints are not named in the available data and should be confirmed against the Frappe GHSA-jp5q-723q-g826 advisory. No user interaction and no special non-default configuration are indicated, so any deployment running an affected version (before 15.119.1, or 16.x before 16.32.0) with normal user accounts is exposed. The principal limiting factor is the authentication requirement; impact is confined to reading data, not modification or service disruption.

This is a moderate-priority vulnerability rather than an emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) confirms a network-reachable, low-complexity attack, but PR:L establishes that authentication with low privileges is required - this is not an unauthenticated remote flaw, which meaningfully narrows the attacker pool to users who already possess valid (even if low-privileged) ERPNext credentials. Impact is confidentiality-only (VC:H/VI:N/VA:N), consistent with a read-oriented SQL injection used to extract data rather than to modify records or disrupt availability. No EPSS score, CISA KEV listing, or public POC is present in the provided intelligence, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The 7.1 score is driven largely by the high confidentiality impact over a network vector; the authentication requirement is the primary mitigating signal. No signals are directly conflicting, but a key gap exists: the specific vulnerable endpoints are not enumerated in the available data, so exposure cannot be precisely scoped - verify affected endpoints against the Frappe GHSA advisory.

A user holding a low-privilege ERPNext account (or an attacker who has phished/obtained such credentials) sends a specially crafted request to one of the affected endpoints that lacks input validation, injecting SQL that alters the backend query. The malicious query returns database contents the user is not authorized to see, enabling extraction of sensitive records such as customer, financial, or HR data. No public exploit code is identified at time of analysis, so an attacker would need to craft the injection manually.