SQL Injection in Frappe HR (CVE-2026-54524)
Summary
SQL injection in Frappe HR (CVE-2026-54524). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 16.7.0 or later.
Original description
The description as published by the source.
Frappe HR is an open-source human resources management solution (HRMS). Prior to 16.7.0, an authenticated user with the HR User role can inject SQL through filters in the Salary Payments Based on Payment Mode report. In hrms/payroll/report/salary_payments_based_on_payment_mode/salary_payments_based_on_payment_mode.py, get_conditions constructs filter clauses from user-controlled values and get_data incorporates those clauses into a string-formatted SQL query, allowing extraction of arbitrary database data. This issue is fixed in 16.7.0.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54524 has been found in Frappe HR.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Frappe HR to 16.7.0 or later.
If unsure, ask your IT team or search "Frappe HR CVE-2026-54524" on the vendor's site.
CVE-2026-54524 (Frappe HR) — CWE-89
Patched: 16.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in Frappe HR.
Check the vendor advisory for the affected versions of Frappe HR.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 16.7.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Frappe HR を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Frappe HR to 16.7.0ステージング環境で 16.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。