dbcve.org
FineractApplication · Apache

CVE-2018-1289

HIGH · 8.8 CVSS v3.0 Published 2018-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In Apache Fineract versions 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, the system exposes different REST end points to query domain specific entities with a Query Parameter 'orderBy' and 'sortOrder' which are appended directly with SQL statements. A hacker/user can inject/draft the 'orderBy' and 'sortOrder' query parameter in such a way to read/update the data for which he doesn't have authorization.

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 REST endpoints expose 'orderBy' and 'sortOrder' query parameters that are directly concatenated into SQL statements without parameterization or input validation, enabling SQL injection attacks to read or modify unauthorized data.

MitigationImplement parameterized queries or prepared statements for orderBy/sortOrder parameters and add strict input validation to whitelist allowed column names and sort directions.

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:= 0.4.0= 0.5.0= 0.6.0= 1.0.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
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 checks

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

  1. Identify Apache Fineract installation and version
    Locate the fineract-server.war file or check the application's manifest/banner for version information. In a deployment directory, look for version identifiers in WAR file names, build files, or configuration files.
    Affected if The installed version matches 0.4.0, 0.5.0, 0.6.0, or 1.0.0 exactly
  2. Verify REST API endpoints are exposed
    Check if the Fineract REST API is accessible by attempting to reach typical endpoints such as /fineract-provider/api/v1/ or checking the deployed application's exposed servlets in web.xml or similar configuration.
    Affected if REST API endpoints are publicly or internally accessible without additional access controls
  3. Identify usage of orderBy and sortOrder parameters
    Review application logs, traffic captures, or API client code for requests that include 'orderBy' or 'sortOrder' query parameters in API calls to Fineract endpoints.
    Affected if Applications or users are sending requests with orderBy or sortOrder query parameters to Fineract API endpoints
  4. Confirm lack of parameterized query enforcement
    Examine the application source code or decompiled classes for the API endpoint handlers that process sorting parameters. Look for string concatenation of these parameters into SQL queries rather than prepared statement usage.
    Affected if Code analysis reveals direct string concatenation of orderBy/sortOrder into SQL without input validation or parameter binding

You are affected if Fineract version 0.4.0, 0.5.0, 0.6.0, or 1.0.0 is installed AND the REST API is accessible AND applications use orderBy/sortOrder query parameters without code-level safeguards against SQL injection.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for orderBy/sortOrder parameters and add strict input validation to whitelist allowed column names and sort directions.

Fix this in Fineract Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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 locally
dbcve dependency scanner

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