Skip to main content
Menu
CVEs

CVE

HRMS authorization bypass in roster get_events

CVE-2026-130794EUVD-2026-127279GHSA-PPX2-PV7C-QXCW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

5.3MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 16.9.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 16.9.0.

Published
Last modified
Reference
Last checked
23/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

Summary

Frappe HR (hrms) contains a missing authorization flaw in its roster get_events method that lets a logged-in employee bypass User Permissions and view other employees' leave and shift data. The attack can be carried out remotely by any account with the Employee role.

Written by a model from the sources below. Verify against them.

Original description

Frappe HR (hrms) before 16.9.0 contains a missing authorization vulnerability in the hrms.api.roster.get_events method that allows authenticated employees to view other employees' leave and shift data by bypassing User Permissions. Attackers with the Employee role can call get_events with empty filters for any date range to retrieve every employee's approved leave applications and shift assignments, including leave types, dates, shift locations and times.

cve.now Index

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 16.9.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-130794 (Frappe HR (hrms) before 16.9.0 Missing Authorization via Roster get_events), 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-130794 (entry last updated 2026-11-17):
Affected:
- frappe hrms: fixed in 16.9.0
Fixed versions: 16.9.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130794 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130794 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/commit/65e04cc5a251a0f3447ff74d28659387b840a810
- https://github.com/frappe/hrms/pull/4651
- https://github.com/frappe/hrms/blob/v16.8.0/hrms/api/roster.py#L271-L344
- https://github.com/frappe/hrms/releases/tag/v16.9.0
- https://www.vulncheck.com/advisories/frappe-hr-hrms-before-16.9.0-missing-authorization-via-roster-get-events
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-130794
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-130794"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • frappe hrms

    fixed in 16.9.0

Evidence 8

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 5

  1. Patch
  2. Patch
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130794

Is CVE-2026-130794 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130794?

hrms: before 16.9.0.Source: cve.now feed data

How do I fix CVE-2026-130794?

Upgrade to a fixed version: 16.9.0.Source: cve.now feed data

More CVEs