dbcve.org
FineractApplication · Apache

CVE-2025-58137

HIGH · 8.1 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 1.12.1 or later.
See remediation →
87/100
Remediation priority · High
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
Authorization Bypass Through User-Controlled Key vulnerability in Apache Fineract. This issue affects Apache Fineract: through 1.11.0. The issue is fixed in version 1.12.1. Users are encouraged to upgrade to version 1.13.0, the latest release.

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 · moderate confidence

This is an Authorization Bypass Through User-Controlled Key vulnerability in Apache Fineract up to version 1.11.0. Attackers can manipulate user-controlled keys to bypass authorization checks and gain unauthorized access to functionality or data that should be restricted.

MitigationUpgrade Apache Fineract to version 1.12.1 or later (1.13.0 recommended) to remediate this vulnerability. Prioritize testing of all authorization controls after the upgrade.

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.12.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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 version
    Locate the Fineract installation and retrieve the version number from the deployed binaries, WAR file, or system information (for example, check the build manifest, version file, or admin UI if available).
    Affected if The installed version is lower than 1.12.1 (for example, 1.11.0, 1.10.x, or earlier).
  2. Confirm user-controlled key authorization is in use
    Review application code or configuration to determine whether authorization logic processes user-supplied keys, identifiers, or parameters that could influence access decisions.
    Affected if The system uses user-controlled keys or parameters in authorization checks without proper validation.
  3. Assess network exposure of sensitive endpoints
    Determine whether the Fineract API or web interface is exposed to untrusted networks or accessible without strong authentication.
    Affected if The application is network-accessible to untrusted users without additional access controls.

You are affected if your installed Apache Fineract version is below 1.12.1 and the application uses user-controlled keys in its authorization logic with network exposure.

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.12.1 or later
Fixed in 1.12.1
Interim mitigation

Upgrade Apache Fineract to version 1.12.1 or later (1.13.0 recommended) to remediate this vulnerability. Prioritize testing of all authorization controls after the upgrade.

Recommended fix High confidence

1.12.1 (recommended: 1.13.0)

  1. Backup the current Apache Fineract installation and database before proceeding with any upgrade
  2. Download Apache Fineract version 1.12.1 (or 1.13.0 as the latest release) from the official Apache Fineract distribution repository
  3. Review the upgrade documentation specific to your deployment method (standalone or Kubernetes)
  4. Stop the running Fineract services
  5. Execute the database migration scripts included in the new version
  6. Deploy the new Fineract 1.12.1+ binaries
  7. Start the Fineract services and verify the application is operational
  8. Test that the authorization bypass vulnerability is resolved by verifying that users cannot access resources via manipulated identifiers

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

Fix this in Fineract Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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