CVE-2026-40888
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFrappe HR is an open-source human resources management solution (HRMS). Prior to versions 15.58.1 and 16.4.1, an authenticated user with default role can access unauthorized information by exploiting certain api endpoint. Versions 15.58.1 and 16.4.1 contain a patch. No known workarounds are available.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceFrappe HR versions prior to 15.58.1 and 16.4.1 contain an Insecure Direct Object Reference (IDOR) or broken access control vulnerability where authenticated users with default roles can access unauthorized information through certain API endpoints. This is an information disclosure vulnerability requiring authentication but exploiting insufficient authorization checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 15.58.1>= 16.0.0, < 16.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Frappe HR versionAccess the Frappe desk, navigate to 'Help' > 'About', or query the database: SELECT value FROM `tabSingles` WHERE doctype = 'System' AND field = 'app_version' for the Frappe HR app.Affected if The version is below 15.58.1 OR is 16.x.x below 16.4.1.
-
Verify default roles are in useNavigate to 'Settings' > 'User' > 'Roles' or query: SELECT DISTINCT(role) FROM `tabUserRole` WHERE role IN ('Employee', 'Leave Approver', 'Employee Self Service').Affected if Default roles like Employee, Leave Approver, or Employee Self Service exist and are assigned to users.
-
Confirm API endpoints are reachableTest accessing HR API endpoints (e.g., /api/method/hrms.api.get_employee_details or similar HR-related API routes) using an authenticated session with only default roles.Affected if API endpoints return HR data for employees other than the logged-in user without proper authorization checks.
-
Check for unauthorized data accessUsing a low-privilege account (with only Employee role), attempt to query HR records of other users via API and verify if sensitive information is returned.Affected if Data from other employees or sensitive HR records are accessible to users who should not have access.
A user is affected if their Frappe HR version is below 15.58.1 or below 16.4.1 AND authenticated users with default roles can access HR data of other employees through API endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.58.116.4.1
Upgrade Frappe HR to version 15.58.1 or 16.4.1 which contains the patch. No workarounds are available.
Upgrade to Frappe HR version 15.58.1 (for v15.x branch) or 16.4.1 (for v16.x branch)
- 1. Identify the current Frappe HR version installed in your environment
- 2. If running version 15.x (< 15.58.1), upgrade to version 15.58.1
- 3. If running version 16.x (>= 16.0.0 and < 16.4.1), upgrade to version 16.4.1
- 4. Verify the upgrade completed successfully by checking the version number
- 5. Test that the application functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40888 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data