CVE-2026-40889
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.2 and 16.4.2, authenticated users can access unauthorized files by exploiting certain api endpoint. Versions 15.58.2 and 16.4.2 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 · high confidenceFrappe HR versions prior to 15.58.2 and 16.4.2 contain an insecure direct object reference (IDOR) vulnerability in a specific API endpoint that allows authenticated users to access files outside their authorized scope. This is an authorization bypass that enables unauthorized file disclosure to any user with valid credentials.
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.2>= 16.0.0, < 16.4.2CVSS 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.1/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 Frappe HR versionCheck the installed Frappe HR version via the command bench get-version or by inspecting the apps/hrms/apps.txt file in the Frappe bench directoryAffected if The installed version is below 15.58.2 (for 15.x branch) or >= 16.0.0 but below 16.4.2 (for 16.x branch)
-
Confirm Frappe HR app is in useRun bench list-apps to verify the hrms app is installed and note its version numberAffected if The hrms app is present and its version falls within the affected ranges
-
Locate the vulnerable API endpointSearch the Frappe HR source code in apps/hrms/hrms for API route handlers that handle file operations, typically under api/ or controller/ paths, and look for endpoints accepting file path or document name parameters without proper authorization checksAffected if An API endpoint exists that accepts object identifiers (such as file paths or document names) as parameters without validating user authorization to access those specific objects
-
Test authorization boundaryUsing an authenticated user account with limited permissions (such as an Employee user), attempt to access files or documents belonging to a different employee or restricted area through the suspected API endpointAffected if The API returns file content or document data that the test user should not have permission to access, indicating the IDOR vulnerability is present
If Frappe HR version is below 15.58.2 or between 16.0.0 and 16.4.2, and the file access API endpoint allows unauthorized access to files outside the authenticated user's scope, the environment is vulnerable to CVE-2026-40889.
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.216.4.2
Upgrade Frappe HR to version 15.58.2 (for the 15.x branch) or version 16.4.2 (for the 16.x branch). No workarounds are available.
15.58.2 (for 15.x branch) or 16.4.2 (for 16.x branch)
- Identify the current Frappe HR version branch (15.x or 16.x) by checking the installed version
- If using Frappe HR 15.x branch (version < 15.58.2): Upgrade to version 15.58.2 or later
- If using Frappe HR 16.x branch (version >= 16.0.0 and < 16.4.2): Upgrade to version 16.4.2 or later
- Verify the upgrade was successful by checking the new version number after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40889 — 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-40889 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