dbcve.org
FineractApplication · Apache

CVE-2018-11801

CRITICAL · 9.8 CVSS v3.0 Published 2019-06-11
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Apache Fineract before 1.3.0 allows attackers to execute arbitrary SQL commands via a query on a m_center data related table.

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 attackers to execute arbitrary SQL commands via a query on the m_center data table. The vulnerability exists in versions before 1.3.0 and stems from improper input validation or unsanitized parameter handling in the SQL query construction.

MitigationUpgrade Apache Fineract to version 1.3.0 or later. Until then, implement input validation and parameterized queries for all database interactions involving the m_center table.

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.3.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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
    Locate the Fineract installation directory and check for version file or build configuration. Common locations include the root directory with a 'version' file, or check the WAR file manifest. You can also query the API endpoint if available: /api/v1/_queries/version or inspect pom.xml/build.gradle for version information.
    Affected if Apache Fineract is installed and the version cannot be determined or is found to be below 1.3.0
  2. Compare installed version to affected range
    Review the identified version number against the affected range of versions before 1.3.0. Check pom.xml, gradle.properties, or the version endpoint response for the exact version string.
    Affected if The installed version is any release prior to 1.3.0 (for example, 1.2.0, 1.1.0, 1.0.x, etc.)
  3. Verify m_center table presence
    Connect to the underlying database used by Fineract (MySQL, PostgreSQL, etc.) and check if the m_center table exists. Run a query like: SELECT table_name FROM information_schema.tables WHERE table_name = 'm_center';
    Affected if The m_center table exists in the database, indicating the vulnerable code path may be reachable
  4. Identify application entry points
    Review the application configuration and deployed API endpoints to determine if the m_center table query functionality is exposed through the REST API or any web interface. Check API documentation or exposed endpoints for endpoints that query the m_center table.
    Affected if The application has active API endpoints or interfaces that process queries against the m_center table

You are affected if Apache Fineract version is below 1.3.0 AND the m_center table is present and accessible through the application.

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.3.0 or later
Fixed in 1.3.0
Interim mitigation

Upgrade Apache Fineract to version 1.3.0 or later. Until then, implement input validation and parameterized queries for all database interactions involving the m_center table.

Recommended fix Moderate confidence

1.3.0

  1. 1. Back up the existing Fineract installation and database before proceeding with any upgrade
  2. 2. Download Apache Fineract version 1.3.0 or later from the official Apache Fineract distribution repository
  3. 3. Review the official Apache Fineract upgrade documentation for your specific deployment method
  4. 4. Test the upgrade in a staging or development environment to verify functionality
  5. 5. Apply the upgrade to production environment during a scheduled maintenance window
  6. 6. Verify the SQL injection vulnerability is resolved by testing queries against the m_center data tables

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

Fix this in Fineract Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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