Quick answers
- Is CVE-2026-57821 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57821 being exploited in the wild.
- How severe is CVE-2026-57821?
- Informational severity, with a CVSS score of 0, published 15 July 2026.
- Which products and versions are affected?
- Apache Software Foundation Fineract <= 1.14.0.
- Is there a fix for CVE-2026-57821?
- A patch was published on 2026-06-27: Pull request for fix submitted to GitHub Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57821 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57821?
- Check whether you run Apache Software Foundation Fineract 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 Apache Fineract Office Search API (GET /api/v1/offices) due to improper validation of the 'orderBy' request parameter. The parameter is concatenated directly into SQL queries, bypassing a previous fix (CVE-2024-32838) because the ColumnValidator failed to detect subqueries in the ORDER BY clause. An authenticated attacker with office-viewing permissions can perform time-based blind SQL injection to exfiltrate data. Additionally, concurrent exploitation can exhaust the database connection pool, leading to a denial of service (DoS). The issue is fixed in version 1.15.0 by implementing a strict allowlist for the 'orderBy' parameter.
Affected products
- Apache Software Foundation Fineract <= 1.14.0
Timeline
- 2026-06-27: patched: Pull request for fix submitted to GitHub
- 2026-06-29: other: Fix merged into develop branch
- 2026-07-15: advisory: CVE published by NVD