dbcve.org
FineractApplication · Apache

CVE-2026-56287

HIGH · 8.1 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 1.15.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Boolean-based SQL injection in Apache Fineract's Client Search API (GET /api/v1/clients) where the orderBy and sortOrder parameters are concatenated directly into SQL queries without validation, allowing authenticated users with client view permissions to inject arbitrary SQL and extract data via blind boolean techniques or read arbitrary files on MySQL/MariaDB using LOAD_FILE().

MitigationUpgrade to a version containing the fix (versions after 1.14.0) and implement proper input validation or parameterized queries for orderBy and sortOrder parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FineractApplication
Affected:< 1.15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Fineract installation version
    Locate the version file or build configuration (e.g., build.gradle, version.info, or the Fineract admin interface). Common paths include the root directory or WEB-INF/lib jar filenames.
    Affected if The installed version is lower than 1.15.0 (e.g., 1.14.0 or earlier)
  2. Confirm Client Search API is exposed
    Verify the endpoint GET /api/v1/clients is accessible in your deployment. Check the API routing configuration or attempt a request to the endpoint with valid credentials.
    Affected if The API endpoint exists and accepts requests (the vulnerability exists regardless of exposure, but exploitation requires this endpoint)
  3. Verify authentication is configured for the API
    Check that the Fineract API requires authentication. Review the security configuration files (e.g., security config XML, Spring Security config) for client search endpoint protection.
    Affected if The endpoint is protected by authentication (the CVE states it requires authenticated users with client view permissions)
  4. Inspect application logs for suspicious API requests
    Review web server and Fineract application logs for unusual query patterns in GET /api/v1/clients requests, especially where orderBy or sortOrder parameters contain SQL syntax like AND, OR, or LOAD_FILE().
    Affected if Log entries show SQL injection attempts or unusual orderBy/sortOrder values in client search requests

You are affected if Apache Fineract version is below 1.15.0 and the Client Search API is accessible to authenticated users with client view permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.15.0 or later
Fixed in 1.15.0
Interim mitigation

Upgrade to a version containing the fix (versions after 1.14.0) and implement proper input validation or parameterized queries for orderBy and sortOrder parameters.

Recommended fix High confidence

1.15.0

  1. 1. Verify current Fineract version by checking the application's version endpoint or deployment configuration
  2. 2. Review existing backup procedures and ensure recent database backups exist before upgrading
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Download Apache Fineract version 1.15.0 or later from the official Apache Fineract repository (https://github.com/apache/fineract)
  5. 5. Follow the official upgrade instructions in the Fineract documentation for your deployment method
  6. 6. After upgrade, verify the application starts successfully and all services are operational
  7. 7. Test the Client Search API (GET /api/v1/clients) with various orderBy parameters to confirm the vulnerability is patched
  8. 8. Verify that users with client view permissions can still use sorting functionality normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fineract Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56287 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data