dbcve.org
FineractApplication · Apache

CVE-2026-57821

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 SQL Injection vulnerability exists in Apache Fineract's Office Search API (GET /api/v1/offices) in versions up to and including 1.14.0. The orderBy request parameter is concatenated into a SQL query without sufficient validation, allowing an authenticated user with permission to view offices to inject arbitrary SQL via a crafted orderBy value. This is a bypass of the ColumnValidator fix introduced for CVE-2024-32838, which does not detect bare subqueries in the ORDER BY position. This can be leveraged to perform time-based blind SQL injection for data exfiltration. Because the injected query blocks the database connection for its full duration, concurrent exploitation can exhaust the application's database connection pool, resulting in denial of service for other users. 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

Apache Fineract 1.14.0 and earlier contain a SQL injection vulnerability in the GET /api/v1/offices endpoint where the orderBy parameter is directly concatenated into SQL queries without adequate validation, allowing authenticated users with office viewing permissions to inject arbitrary SQL including time-based blind subqueries. This vulnerability bypasses the ColumnValidator fix from CVE-2024-32838 by exploiting bare subqueries in the ORDER BY clause, enabling both data exfiltration and denial of service through database connection pool exhaustion.

MitigationUpgrade to an Apache Fineract version containing the fix for this vulnerability. As an interim measure, consider restricting or disabling the orderBy parameter functionality at the API gateway level until the upgrade is completed.

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
None
Availability
High

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

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 installed Apache Fineract version
    Locate the version file or build artifact - check pom.xml, build.gradle, or the fineract-version.txt file typically found in the installation directory. Run: find . -name 'pom.xml' -exec grep -l '<version>' {} \; or check /opt/fineract/version.properties
    Affected if The version is 1.14.0 or earlier, or if the version cannot be determined and is suspected to be from before 1.15.0
  2. Verify API endpoint /api/v1/offices is exposed
    Check the API gateway or reverse proxy configuration (nginx.conf, httpd.conf) and fineract-security.xml for URL mappings. Attempt a curl request to the endpoint with valid authentication: curl -k https://YOUR_HOST/api/v1/offices
    Affected if The /api/v1/offices endpoint is accessible and responds to GET requests without returning 404 or 403 at the routing level
  3. Confirm orderBy parameter handling in request flow
    Examine the source code for OfficesApiResource.java or OfficeServiceImpl.java to verify if the orderBy parameter is passed directly to a SQL query builder without validation. Check for patterns like 'ORDER BY ' + orderBy or queryBuilder.orderBy(orderBy) without parameterized binding
    Affected if The orderBy parameter is concatenated directly into SQL ORDER BY clauses without using allowlisted column names or parameterized queries
  4. Check user authentication and office permission configuration
    Review the security configuration files (typically in src/main/resources) and database tables m_permission and m_role_permission to determine if standard authenticated users have office:read permission. Query: SELECT p.code FROM m_permission p WHERE p.code LIKE '%office%'
    Affected if Standard authenticated users with basic office viewing permissions (office:read) can access the vulnerable endpoint
  5. Inspect database query logging for suspicious patterns
    Enable debug logging for SQL statements in logback.xml or application.yml. Review logs for queries containing ORDER BY with subqueries or time-based functions like SLEEP() or BENCHMARK() originating from the offices endpoint
    Affected if Database logs show ORDER BY clauses with subqueries, time delays, or unexpected complexity matching the injection patterns described

You are affected if Apache Fineract version is 1.14.0 or earlier AND the /api/v1/offices endpoint is accessible to authenticated users with office viewing permissions, with the orderBy parameter flowing directly into SQL without validation.

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 an Apache Fineract version containing the fix for this vulnerability. As an interim measure, consider restricting or disabling the orderBy parameter functionality at the API gateway level until the upgrade is completed.

Recommended fix High confidence

1.15.0

  1. Verify current Fineract version by checking the deployed WAR file or build configuration
  2. Back up the existing database and application configuration files
  3. Stop the Fineract application and any running scheduled jobs
  4. Replace the existing Fineract deployment with version 1.15.0
  5. Review and update any custom configurations that may have changed between versions
  6. Start the Fineract application and verify successful startup
  7. Log in and test the Office Search API (GET /api/v1/offices) with both normal and crafted orderBy values to confirm the fix blocks injection
  8. Verify database connection pool behavior under concurrent requests
Caveat Review release notes for 1.15.0 to check for breaking changes in API contracts or configuration formats

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

Fix this in Fineract Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57821 — 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-57821 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