dbcve.org
FineractApplication · Apache

CVE-2025-58130

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 1.12.1 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
Insufficiently Protected Credentials 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

Apache Fineract versions through 1.11.0 contain an Insufficiently Protected Credentials vulnerability, allowing attackers to access sensitive authentication credentials due to inadequate encryption, hashing, or protection mechanisms in the system.

MitigationUpgrade Apache Fineract to version 1.13.0 (latest release) to remediate this critical vulnerability. Prioritize this upgrade given the CVSS 9.1 severity and potential for complete system compromise.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine Apache Fineract installed version
    Check the version file or startup logs for Apache Fineract. Common locations include version properties files or the admin interface dashboard.
    Affected if The installed version is 1.11.0 or lower, or any version prior to 1.12.1
  2. Locate credential storage configuration
    Inspect the configuration files for authentication and user management modules. Look for settings related to password storage, API key handling, or credential encryption.
    Affected if Credentials are configured to be stored without strong encryption or hashing enabled
  3. Verify encryption mechanism on sensitive credentials
    Examine the application's security configuration for evidence of password hashing algorithms (such as bcrypt, scrypt, or Argon2) or encryption for stored credentials.
    Affected if No recognized hashing algorithm or encryption is applied to stored credentials, or weak mechanisms (like MD5 or SHA1 without salt) are in use
  4. Check credential protection settings in security config
    Review the fineract-security.xml or equivalent security configuration file for credential protection parameters and verify if encryption is explicitly enabled.
    Affected if Credential protection/encryption settings are disabled, missing, or set to plaintext storage

A user is affected if Apache Fineract version is below 1.12.1 AND credentials are stored without adequate encryption or hashing protection enabled in the configuration.

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.13.0 (latest release) to remediate this critical vulnerability. Prioritize this upgrade given the CVSS 9.1 severity and potential for complete system compromise.

Recommended fix High confidence

1.13.0

  1. 1. Back up your current Apache Fineract installation and database before upgrading
  2. 2. Download Apache Fineract version 1.13.0 (the latest recommended release) from the official Apache Fineract repository or Apache mirrors
  3. 3. Stop the running Fineract instance
  4. 4. Apply the upgrade by following the standard Fineract upgrade procedure for your deployment method
  5. 5. Ensure the upgraded version is 1.12.1 or higher (1.13.0 recommended)
  6. 6. Verify that credentials are now properly protected and the application starts successfully
  7. 7. Test that authentication and authorization functionality works correctly post-upgrade

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

Fix this in Fineract Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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