# CVE-2026-57821: Apache Fineract: Office list: SQL Injection via Subquery in orderBy

> Authenticated users can inject SQL via the orderBy parameter in Apache Fineract to exfiltrate data or cause denial of service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-wq49-6h5f-gc65

## What is CVE-2026-57821?

CVE-2026-57821 is a high-severity SQL injection vulnerability in Apache Fineract, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-57821?

It affects 1 product.


Products: Apache Fineract.

## How do I fix CVE-2026-57821?

No fix has been published for CVE-2026-57821 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57821 being exploited?

There is no known exploitation of CVE-2026-57821 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-57821 - Apache Fineract SQL Injection Toolkit. Two Python scripts for authorized security testing: verifier.py (safe detection, no extraction) and exploit.py (deep analysis). Supports 11 DB types. Perfect for understanding SQL injection vulnerabilities. Only legal tests for educational & research purposes only. (github_poc): https://github.com/tc4dy/CVE-2026-57821-PoC-Exploit

## Other vulnerabilities in Apache Fineract

- [CVE-2024-23538](https://insights.sbomify.com/CVE-2024-23538/): SQL injection in Apache Fineract (critical 9.9)
- [CVE-2018-11800](https://insights.sbomify.com/CVE-2018-11800/): SQL injection in Apache Fineract (critical 9.8)
- [CVE-2018-11801](https://insights.sbomify.com/CVE-2018-11801/): SQL injection in Apache Fineract (critical 9.8)
- [CVE-2018-1290](https://insights.sbomify.com/CVE-2018-1290/): SQL injection in Apache Fineract (critical 9.8)
- [CVE-2024-32838](https://insights.sbomify.com/CVE-2024-32838/): Apache Fineract: SQL injection vulnerabilities in offices API endpoint (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57821 and fix it if it is affected.

What it is: CVE-2026-57821 is a high-severity SQL injection vulnerability in Apache Fineract, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57821 in the wild and no public exploit code.

Affected product: Apache Fineract. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57821/ (Markdown: https://insights.sbomify.com/CVE-2026-57821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57821
- OSV: https://osv.dev/vulnerability/CVE-2026-57821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57821/
Summaries are generated and may contain mistakes; the official description above is the record.