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-108732 Overview
CVE-2026-108732 is a missing authorization vulnerability [CWE-862] in Frappe HR (hrms) before version 16.11.0, including all 14.x and 15.x releases through 15.64.3. The whitelisted get_account_and_amount method does not enforce role-based permission checks. Authenticated users without HR roles can call the method through /api/method and enumerate Salary Slip or claim document names. This disclosure exposes other employees' net pay along with loan, advance, and claim balances to any logged-in account.
Critical Impact
Any authenticated Frappe user can read payroll amounts and employee claim balances by invoking an unprotected whitelisted API method with enumerable document names.
Affected Products
- Frappe HR (hrms) 14.x releases up to and including 14.x through the end of the branch
- Frappe HR (hrms) 15.x releases up to and including 15.64.3
- Frappe HR (hrms) 16.x releases prior to 16.11.0
Discovery Timeline
- 2026-10-11 - CVE-2026-108732 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-108732
Vulnerability Analysis
Frappe HR exposes server-side Python functions to HTTP clients using the @frappe.whitelist() decorator. Whitelisted methods become reachable through the /api/method/<module.function> endpoint for any authenticated session. The get_account_and_amount helper used by the Full and Final Statement workflow returns payroll figures tied to a document name supplied by the caller.
The function did not call frappe.has_permission() before returning data. Any authenticated user, including low-privilege staff without HR roles, could request payroll amounts belonging to arbitrary Salary Slip or claim records. Document names in Frappe follow predictable naming series, so attackers can enumerate IDs and build a payroll oracle covering the entire workforce.
The disclosed fields include employee net pay, outstanding loan balances, advance balances, and claim totals. The flaw is a server-side authorization gap, not a client-side control, so UI-level hiding does not mitigate exposure.
Root Cause
The root cause is a missing authorization check inside a whitelisted API method. Frappe's whitelist decorator only confirms that the caller is authenticated; it does not evaluate document-level permissions. Developers must explicitly call frappe.has_permission(doctype, "read", name, throw=True) on every record a method returns. Several helper methods in hrms/api/ lacked that call.
Attack Vector
Exploitation requires a valid Frappe session with any role. The attacker sends a POST or GET request to /api/method/hrms.hr.doctype.full_and_final_statement.full_and_final_statement.get_account_and_amount with a target document name. The server returns payroll amounts without validating that the caller holds HR Manager, HR User, or an equivalent role bound to the record.
The upstream commit 6ab7a50347367413b78ad5bd5d9e4b8c6653c81f adds the missing permission guard across multiple whitelisted helpers. Two representative hunks from the patch are shown below.
@frappe.whitelist()
def get_company_cost_center_and_expense_account(company: str) -> dict:
+ frappe.has_permission("Company", "read", company, throw=True)
return frappe.db.get_value(
"Company", company, ["cost_center", "default_expense_claim_payable_account"], as_dict=True
)
Source: Frappe HRMS Commit 6ab7a50
@frappe.whitelist()
def get_schedule_from_assignment(shift_schedule_assignment: str):
+ frappe.has_permission("Shift Schedule Assignment", "read", shift_schedule_assignment, throw=True)
shift_schedule = frappe.db.get_value(
"Shift Schedule Assignment", shift_schedule_assignment, "shift_schedule"
)
Source: Frappe HRMS Commit 6ab7a50
The patch inserts frappe.has_permission(..., throw=True) so the method aborts when the caller lacks read permission on the referenced record.
Detection Methods for CVE-2026-108732
Indicators of Compromise
- Repeated HTTP requests to /api/method/hrms.hr.doctype.full_and_final_statement.full_and_final_statement.get_account_and_amount from a single session.
- API traffic from accounts without HR Manager or HR User roles targeting Salary Slip, Expense Claim, Employee Advance, or Loan document names.
- Sequential enumeration patterns in request parameters that match Frappe's HR-SAL- or HR-EXP- naming series.
Detection Strategies
- Parse Frappe web server access logs for calls to whitelisted HRMS helper methods and correlate the caller's role with the targeted doctype.
- Alert on any session that fetches payroll amounts for more employees than the user's own Employee record resolves to.
- Review Frappe Activity Log and Access Log doctypes for high-volume reads of Salary Slip records by non-HR users.
Monitoring Recommendations
- Baseline normal API call rates per role and flag deviations against the get_account_and_amount endpoint.
- Forward Frappe application logs and reverse proxy logs to a central analytics platform for retention and correlation.
- Enable Frappe's rate limiting on /api/method to slow brute-force enumeration of document names.
How to Mitigate CVE-2026-108732
Immediate Actions Required
- Upgrade Frappe HR to version 16.11.0 or later on all production and staging bench environments.
- Audit custom HRMS apps for @frappe.whitelist() methods that return document data without calling frappe.has_permission().
- Rotate any API keys and session tokens for accounts suspected of enumerating payroll data.
Patch Information
The fix is included in Frappe HRMS Release v16.11.0 and shipped in commit 6ab7a50347367413b78ad5bd5d9e4b8c6653c81f. Users on the 14.x and 15.x branches must migrate to 16.11.0, since the advisory confirms all 14.x releases and 15.x releases up to 15.64.3 remain vulnerable. See the VulnCheck Advisory for exposure details.
Workarounds
- Restrict /api/method access to trusted internal networks using a reverse proxy allowlist until the upgrade is applied.
- Temporarily disable the Full and Final Statement workflow by removing the HR User role from non-HR staff and revoking the read permission on Salary Slip for all low-privilege roles.
- Add a custom Frappe hook to wrap get_account_and_amount with an explicit frappe.has_permission() check if an immediate upgrade is not possible.
# Upgrade Frappe HR on a bench deployment
bench get-app hrms --branch version-16
bench --site <site-name> install-app hrms
bench --site <site-name> migrate
bench restart
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

