FineractApplication · Apache
CVE-2017-5663
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 · uneditedIn Apache Fineract 0.4.0-incubating, 0.5.0-incubating, and 0.6.0-incubating, an authenticated user with client/loan/center/staff/group read permissions is able to inject malicious SQL into SELECT queries. The 'sqlSearch' parameter on a number of endpoints is not sanitized and appended directly to the query.
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 confidenceSQL injection vulnerability in Apache Fineract where the 'sqlSearch' parameter on multiple API endpoints is not sanitized and is directly appended to SELECT queries, allowing authenticated users with read permissions to inject arbitrary SQL.
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
= 0.4.0-incubating= 0.5.0-incubating= 0.6.0-incubatingCVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Fineract versionCheck the version file or administrative interface for the installed Apache Fineract version. Common locations include build.gradle, pom.xml, or the system information page in the admin UI.Affected if The installed version is 0.4.0-incubating, 0.5.0-incubating, or 0.6.0-incubating.
-
Locate API endpoints accepting sqlSearch parameterReview API documentation or proxy/HTTP logs to identify which endpoints accept the 'sqlSearch' query parameter. Common endpoints that may accept this parameter include search, client, loan, or savings-related API endpoints.Affected if The system exposes API endpoints that accept the 'sqlSearch' parameter without documented input validation.
-
Verify authentication configurationCheck user role and permission settings to confirm which authenticated users have read permissions to the API endpoints using sqlSearch.Affected if Authenticated users with read-only permissions can access endpoints that accept the sqlSearch parameter.
-
Confirm direct SQL query constructionReview application logs or database query traces when the sqlSearch parameter is used through the API to observe if parameter values are appended directly to SELECT statements without parameterization.Affected if The sqlSearch parameter value is appended directly to SQL queries without sanitization or parameter binding.
A user is affected if they are running Apache Fineract versions 0.4.0-incubating, 0.5.0-incubating, or 0.6.0-incubating and have API endpoints that accept the sqlSearch parameter accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataSanitize and parameterize the 'sqlSearch' parameter input across all affected endpoints, or upgrade to a patched version of Apache Fineract.
Fix this in Fineract
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5663 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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