CVE
HRMS missing authorization in bulk record action
Affects Frappe HRMS 15.0.0 before 15.64.1 and 16.0.0 before 16.19.0, where users with only read access to a related setup record can run bulk actions. Fixed in 15.64.1 and 16.19.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 15.64.1, 16.19.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Frappe HRMS 15.0.0 before 15.64.1, or 16.0.0 before 16.19.0 The attacker has read access to the related setup record, which the default Employee role includes
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.44% · 38th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Frappe HRMS 15.0.0 before 15.64.1 and 16.0.0 before 16.19.0 lacks a write permission check on a bulk record processing action, allowing users with only read access to the related setup record to modify data. Authenticated users with the default Employee role can run the action to create and submit records for every covered employee.
Who should check
Teams running Frappe HRMS 15.x before 15.64.1 or 16.x before 16.19.0, including sites where users hold the Employee role
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
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Frappe HRMS 15.0.0 before 15.64.1, or 16.0.0 before 16.19.0 The attacker has read access to the related setup record, which the default Employee role includesUpgrade to a fixed version: 15.64.1, 16.19.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-126412 (Frappe HRMS 15.0.0 before 15.64.1 Missing Authorization in Bulk Record Action), 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-126412 (entry last updated 2026-11-13):
Affected:
- frappe hrms: from 15.0.0, fixed in 15.64.1
- frappe hrms: from 16.0.0, fixed in 16.19.0
Fixed versions: 15.64.1, 16.19.0.
Conditions (all must be true for the bug to be hit):
- Frappe HRMS 15.0.0 before 15.64.1, or 16.0.0 before 16.19.0 (source: https://www.vulncheck.com/advisories/frappe-hrms-15.0.0-before-15.64.1-missing-authorization-in-bulk-record-action)
- The attacker has read access to the related setup record, which the default Employee role includes (source: https://www.vulncheck.com/advisories/frappe-hrms-15.0.0-before-15.64.1-missing-authorization-in-bulk-record-action)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126412 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126412 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/hrms/security/advisories/GHSA-5643-8fxc-qpm2
- https://www.vulncheck.com/advisories/frappe-hrms-15.0.0-before-15.64.1-missing-authorization-in-bulk-record-action
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-126412
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-126412"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- frappe hrms
From 15.0.0 · fixed in 15.64.1
- frappe hrms
From 16.0.0 · fixed in 16.19.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126412
Is CVE-2026-126412 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?
A user with only read access can run a bulk action that creates and submits records for every employee it covers. The cause is a missing write permission check.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126412?
hrms: from 15.0.0 before 15.64.1. hrms: from 16.0.0 before 16.19.0.Source: cve.now feed data
Am I affected, and how do I check?
Frappe HRMS 15.0.0 before 15.64.1 and 16.0.0 before 16.19.0 are in scope. Check the installed HRMS version to see whether it falls within these ranges.Source: vulncheck.com, github.com
How do I fix CVE-2026-126412?
Upgrade HRMS to 15.64.1 for the 15.x line or to 16.19.0 for the 16.x line. The sources do not name a workaround.Source: vulncheck.com, github.com