Quick answers
- Is CVE-2026-54524 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54524 being exploited in the wild.
- How severe is CVE-2026-54524?
- Informational severity, published 17 September 2026.
- Which products and versions are affected?
- Frappe HR before 16.7.0.
- Is there a fix for CVE-2026-54524?
- A patch was published on 2026-05-11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54524 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-54524?
- Check whether you run Frappe HR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in the Salary Payments Based on Payment Mode report (hrms/payroll/report/salary_payments_based_on_payment_mode/salary_payments_based_on_payment_mode.py). The get_conditions function constructs filter clauses from user-controlled filter parameters, and the get_data function incorporates these unsanitized clauses into a string-formatted SQL query without proper parameterization. An authenticated user with the HR User role can craft malicious filter values to inject arbitrary SQL, enabling extraction of sensitive database data. The vulnerability requires authentication and access to the report functionality. This issue is fixed in version 16.7.0 by refactoring the report to use Frappe's query builder instead of string concatenation.
Affected products
- Frappe HR before 16.7.0
Timeline
- 2026-05-11: patched
- 2026-09-17: disclosed