CVE-2026-41320
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.54.0 and 14.38.1, a specially crafted request made to a certain endpoint could result in SQL injection, allowing an attacker to extract information they wouldn't otherwise be able to. Versions 15.54.0 and 14.38.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 · high confidenceSQL injection vulnerability in Frappe HR allows attackers to inject malicious SQL queries through a specific endpoint, enabling unauthorized extraction of sensitive data from the database. The vulnerability exists in versions prior to 15.54.0 and 14.38.1 and is exploitable via specially crafted HTTP requests.
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< 14.38.1>= 15.0.0, < 15.54.0CVSS 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 installed Frappe HR versionAccess the Frappe system viabench or admin interface and retrieve the installed Frappe HR version number. This is typically shown in the installed apps list or about page.Affected if The installed version is less than 14.38.1, or is 15.0.0 or higher but less than 15.54.0
-
Confirm Frappe HR application is activeVerify that the Frappe HR application module is installed and enabled on the Frappe bench instance.Affected if Frappe HR is installed and running on the affected version ranges listed above
-
Determine if HTTP endpoints are exposedCheck if the Frappe web server is accepting external HTTP requests to HR-related API endpoints. Review site configuration and web server settings.Affected if The HR module endpoints are accessible via HTTP without additional authentication or access controls that would prevent the injection
-
Review application logs for SQL injection patternsExamine Frappe error logs and web server logs for suspicious SQL syntax or database error messages originating from HR-related routes.Affected if SQL injection attempts or unusual database errors are found in logs related to HR endpoints
You are affected if your Frappe HR installation runs version 14.38.1 or lower, or version 15.0.0 through 15.53.x, and the HR module is accessible via HTTP.
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 · scoped14.38.115.54.0
Upgrade Frappe HR to version 15.54.0 or 14.38.1 or later to apply the patch. No workarounds are available.
Frappe HR version 14.38.1 (for 14.x branch) or version 15.54.0 (for 15.x branch)
- Backup your Frappe HR database and site data before upgrading
- Update the Frappe framework (bench) to the latest version: bench update --upgrade
- Navigate to your Frappe HR application directory or use the bench command to update the hrms app: bench get-app hrms
- After updating, migrate your site: bench --site [your-site-name] migrate
- Verify the upgrade was successful by checking the Frappe HR version in the system
- Test critical HR workflows to ensure functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41320 — 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-41320 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