# CVE-2026-65874: Apache Fineract SQL injection in centers and datatables endpoints

Source: https://junglewise.ai/threats/cve-2026-65874-this-issue-affects-apache-fineract-versions-up-to-and-including-1  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-65874 · Severity: info · Published 2026-10-30

Apache Fineract is a microfinance platform that manages customer accounts, loans, and transactions. The application's centers and datatable read APIs accept sorting parameters that are vulnerable to SQL injection attacks. An authenticated user with read access can inject malicious SQL code through ordering parameters to extract sensitive database information via time-based attacks.

Technologies: [Apache Fineract](https://junglewise.ai/threats/technologies/apache-fineract). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-65874 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-65874 being exploited in the wild.

**How severe is CVE-2026-65874?** Informational severity, published 30 October 2026.

**Which products and versions are affected?** Apache Fineract up to and including 1.15.0.

**Is there a fix for CVE-2026-65874?** Yes: fixed in 1.16.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-65874 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-65874?** Check whether you run Apache 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.

## How to fix

- Fixed in 1.16.1

## Technical details

The vulnerability is a time-based blind SQL injection flaw in the GET /api/v1/centers and GET /api/v1/datatables endpoints, where the orderBy, sortOrder, and order parameters are concatenated directly into the SQL ORDER BY clause. Although regex-based input validation exists, it can be bypassed by an authenticated attacker with read access. The fix validates that order parameters reference only actual columns and rejects malformed input.

## Affected products

- Apache Fineract up to and including 1.15.0

## Timeline

- 2026-10-30: disclosed
- 2026-08-18: patched: Fixes merged in pull requests #6230 and #6277 to develop branch; 1.16.1 release available

## References

- [https://github.com/apache/fineract/pull/6230](https://github.com/apache/fineract/pull/6230)
- [https://github.com/apache/fineract/pull/6277](https://github.com/apache/fineract/pull/6277)

## Related threats

- [Apache Fineract SQL injection in search API](https://junglewise.ai/threats/cve-2026-64618-improper-neutralization-of-special-elements-used-in-an-sql)
- [Authorization Bypass Through User-Controlled Key vulnerability in Apache Fineract. This issue affects Apache Fineract…](https://junglewise.ai/threats/cve-2025-58137-authorization-bypass-through-user-controlled-key-vulnerability-in)
- [Insufficiently Protected Credentials vulnerability in Apache Fineract. This issue affects Apache Fineract: through…](https://junglewise.ai/threats/cve-2025-58130-insufficiently-protected-credentials-vulnerability-in-apache)
- [Weak Password Requirements vulnerability in Apache Fineract. This issue affects Apache Fineract: through 1.10.1. The…](https://junglewise.ai/threats/cve-2025-23408-weak-password-requirements-vulnerability-in-apache-fineract-this)