dbcve.org
FineractApplication · Apache

CVE-2026-35152

HIGH · 8.8 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 1.15.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

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
A SQL Injection vulnerability exists in Apache Fineract's Report Execution API (runreports endpoint) in versions up to and including 1.14.0. Report parameter values are incorporated into the generated SQL query without sufficient validation, allowing an authenticated user with permission to run reports to inject arbitrary SQL via crafted parameter values. This can be leveraged to perform unauthorized access to data beyond what the report was designed to expose. Users are recommended to upgrade to a version containing the fix.

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 in Apache Fineract's Report Execution API (runreports endpoint) allows authenticated users with report execution permissions to inject arbitrary SQL through crafted parameter values. Report parameters are incorporated into generated SQL queries without sufficient validation, enabling unauthorized data access beyond the report's intended scope.

MitigationUpgrade Apache Fineract to a version containing the fix. As interim measures, restrict report execution permissions to trusted users only and audit existing reports for suspicious parameter patterns.

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.15.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.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. Determine Apache Fineract installed version
    Locate the version file or check the build artifact in your Fineract deployment directory, or query the API endpoint that returns version information if available
    Affected if The installed version is lower than 1.15.0
  2. Verify runreports endpoint exposure
    Confirm the /api/v1/runreports endpoint is accessible in your Fineract deployment by checking the exposed API routes and reverse proxy configuration
    Affected if The runreports API endpoint is publicly or widely accessible without additional restrictions
  3. Identify users with report execution permissions
    Review the Fineract user roles and permissions configuration to list accounts granted the report execution capability
    Affected if There are user accounts with report execution permissions beyond trusted administrators only
  4. Check existing reports for parameterized queries
    Inspect the saved report definitions in the Fineract database or reports configuration to identify which reports accept user-supplied parameters
    Affected if There are reports configured with parameters that could accept arbitrary input
  5. Audit runreports API access logs
    Review application and API access logs for requests to the runreports endpoint, focusing on parameter values that appear anomalous or contain SQL-like syntax
    Affected if Recent runreports API calls contain unusual parameter patterns suggesting injection attempts

You are affected if Fineract version is below 1.15.0 AND the runreports endpoint is accessible to users with report execution permissions.

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.15.0 or later
Fixed in 1.15.0
Interim mitigation

Upgrade Apache Fineract to a version containing the fix. As interim measures, restrict report execution permissions to trusted users only and audit existing reports for suspicious parameter patterns.

Recommended fix High confidence

1.15.0

  1. Backup the existing Fineract installation and database before proceeding with the upgrade
  2. Download Apache Fineract version 1.15.0 from the official Apache repository (https://archive.apache.org/dist/fineract/)
  3. Stop the running Fineract service to prevent data corruption during upgrade
  4. Deploy the version 1.15.0 binaries to your Fineract installation directory
  5. Run database migration scripts if provided in the release notes (typically located in the db/migration directory)
  6. Start the Fineract service and verify it starts without errors
  7. Test the runreports endpoint with various parameter values to confirm the SQL injection vulnerability is remediated
  8. Verify that existing reports function correctly with the new version

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

Fix this in Fineract Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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