CVE-2026-56287
Received Received - Intake

Boolean-based SQL Injection in Apache Fineract

Vulnerability report for CVE-2026-56287, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-15

Last updated on: 2026-07-15

Assigner: Apache Software Foundation

Description

A boolean-based SQL Injection vulnerability exists in Apache Fineract's Client Search API (GET /api/v1/clients) in versions up to and including 1.14.0. The orderBy and sortOrder request parameters are concatenated into a SQL query without sufficient validation, allowing an authenticated user with permission to view clients to inject arbitrary SQL via a crafted orderBy value. This can be leveraged to perform blind boolean-based data extraction and, on MySQL/MariaDB, to disclose arbitrary files readable by the database process via the LOAD_FILE() function. Users are recommended to upgrade to a version containing the fix

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-15
Last Modified
2026-07-15
Generated
2026-07-15
AI Q&A
2026-07-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
apache fineract to 1.14.0 (inc)

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 is a boolean-based SQL Injection vulnerability in Apache Fineract's Client Search API. It affects versions up to 1.14.0 and allows authenticated users with client viewing permissions to inject malicious SQL via the orderBy parameter. The issue occurs because the orderBy and sortOrder parameters are concatenated into a SQL query without proper validation.

Impact Analysis

An attacker could exploit this to extract sensitive data through blind boolean-based SQL queries. On MySQL/MariaDB databases, they could also read arbitrary files accessible to the database process using the LOAD_FILE() function. This requires an authenticated user with specific permissions.

Compliance Impact

This vulnerability could lead to unauthorized data access, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Exploitation may result in data breaches, triggering compliance violations and potential regulatory penalties.

Detection Guidance

To detect this vulnerability, monitor Apache Fineract API logs for suspicious GET /api/v1/clients requests with unusual orderBy or sortOrder parameters. Check for boolean-based SQL injection patterns like OR 1=1 or AND 1=2 in logs. Use tools like sqlmap to test for SQL injection in the Client Search API endpoint.

Mitigation Strategies

Immediately upgrade Apache Fineract to a version beyond 1.14.0 that includes the fix from pull request #6020. If upgrading is not possible, restrict access to the /api/v1/clients endpoint to trusted users only and implement strict input validation for orderBy and sortOrder parameters.

Chat Assistant

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

EPSS Chart