dbcve.org
FineractApplication · Apache

CVE-2024-32838

HIGH · 8.8 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 1.10.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
SQL Injection vulnerability in various API endpoints - offices, dashboards, etc. Apache Fineract versions 1.9 and before have a vulnerability that allows an authenticated attacker to inject malicious data into some of the REST API endpoints' query parameter.  Users are recommended to upgrade to version 1.10.1, which fixes this issue. A SQL Validator has been implemented which allows us to configure a series of tests and checks against our SQL queries that will allow us to validate and protect against nearly all potential SQL injection attacks.

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

SQL injection vulnerability in Apache Fineract allows authenticated attackers to inject malicious SQL code through query parameters in multiple REST API endpoints including offices and dashboards. The vulnerability exists in versions 1.9 and prior.

MitigationUpgrade to Apache Fineract 1.10.1 or later, which includes a configurable SQL Validator to protect against SQL injection attacks across API endpoints.

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.4.0, < 1.10.1

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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
    Check the Fineract version by reviewing the build configuration file (build.gradle), version manifest, or theAbout API endpoint if available. Run: grep -r 'version' build.gradle | head -5 or check WEB-INF/lib for fineract*.jar manifest.
    Affected if The installed version is 1.9 or prior, or any version >= 1.4.0 and < 1.10.1
  2. Confirm REST API is exposed
    Verify that the Fineract REST API endpoints are accessible. Check the deployment configuration and network accessibility of /api endpoints. Look for exposed API URLs in your configuration files or reverse proxy setup.
    Affected if The REST API endpoints (particularly /api/v1/offices and /api/v1/dashboards) are reachable from the network
  3. Check if API authentication is enforced
    Review the security configuration files (typically in src/main/resources or application properties) for authentication settings. Verify whether the API requires valid credentials by testing unauthenticated access to /api/v1/offices endpoint.
    Affected if API endpoints do not require authentication or use weak authentication that could be bypassed
  4. Inspect SQL query handling for offices and dashboards endpoints
    Review the source code for the offices and dashboards API controllers. Look for direct use of query parameters in SQL statements without proper parameterization. Search for files containing 'OfficeController' or 'DashboardController' and examine their query methods.
    Affected if Query parameters from API requests are concatenated directly into SQL queries without prepared statements or input validation

A user is affected if Fineract version is 1.9 or prior (or any version >= 1.4.0 and < 1.10.1) AND the REST API endpoints for offices/dashboards are accessible to authenticated attackers.

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.10.1 or later
Fixed in 1.10.1
Interim mitigation

Upgrade to Apache Fineract 1.10.1 or later, which includes a configurable SQL Validator to protect against SQL injection attacks across API endpoints.

Recommended fix High confidence

1.10.1

  1. 1. Create a full backup of the current Fineract installation and database before proceeding
  2. 2. Stop the Fineract service to prevent any data inconsistency during the upgrade
  3. 3. Download Apache Fineract version 1.10.1 from the official Apache repository
  4. 4. Upgrade the Fineract installation to version 1.10.1 following the standard upgrade procedure
  5. 5. Verify that the SQL Validator feature is enabled and functioning after the upgrade
  6. 6. Restart the Fineract service and confirm all API endpoints are operational
  7. 7. Test the previously vulnerable API endpoints (offices, dashboards, etc.) to confirm the SQL injection vulnerability is resolved

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

Fix this in Fineract Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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