CVE-2026-65874
Received Received - Intake

Blind SQL Injection in Apache Fineract

Publication date: 2026-10-30

Last updated on: 2026-10-30

Assigner: Apache Software Foundation

Description
This issue affects Apache Fineract versions up to and including 1.15.0. The Center read endpoint (GET /api/v1/centers) and the datatable entry read endpoints (GET /api/v1/datatables/{datatable}/{apptableId} and GET /api/v1/datatables/{datatable}/{apptableId}/{datatableId}) concatenate caller-supplied ordering parameters (orderBy, sortOrder, order) directly into the SQL ORDER BY clause. The existing regex-based input validation can be bypassed, allowing time-based blind SQL injection by any authenticated user with read access to centers or to the targeted datatable. Users are recommended to upgrade to 1.16.1 which fixes the issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-30
Last Modified
2026-10-30
Generated
2026-10-30
AI Q&A
2026-10-30
EPSS Evaluated
N/A
NVD
CVE-2026-65874
EUVD
EUVD-2026-113749

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Apache Software Foundation Apache Fineract 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Apache Fineract versions up to 1.15.0. It allows authenticated users with read access to perform time-based blind SQL injection through improperly validated ordering parameters in specific endpoints. The issue occurs because user-supplied parameters like orderBy, sortOrder, and order are directly concatenated into SQL ORDER BY clauses without sufficient sanitization.

Detection Guidance

To detect this vulnerability, monitor for SQL injection attempts in Apache Fineract endpoints. Check logs for unusual GET requests to /api/v1/centers or /api/v1/datatables with parameters like orderBy, sortOrder, or order containing SQL keywords (e.g., UNION, SELECT, OR). Use tools like SQLMap to test for blind SQL injection by sending crafted orderBy parameters.

Impact Analysis

An attacker could exploit this to extract sensitive data from the database, modify or delete data, or gain unauthorized access to other users' information. Since it requires only read access, the attack surface is broader than typical SQL injection vulnerabilities.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating confidentiality requirements in GDPR and HIPAA. Organizations using affected versions may face compliance violations, data breach notifications, and potential fines if exploited.

Mitigation Strategies

Upgrade Apache Fineract to version 1.16.1 or later to apply the security fixes. If upgrading is not immediately possible, restrict access to the affected endpoints (/api/v1/centers and /api/v1/datatables) to trusted users only. Implement strict input validation for orderBy, sortOrder, and order parameters to reject any non-alphanumeric values.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-65874. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart