dbcve.org
FineractApplication · Apache

CVE-2025-23408

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 1.11.0 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Weak Password Requirements vulnerability in Apache Fineract. This issue affects Apache Fineract: through 1.10.1. The issue is fixed in version 1.11.0. 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 through version 1.10.1 contains weak password requirements that could allow attackers to compromise user accounts using easily guessable passwords. The vulnerability stems from insufficient password policy enforcement in the authentication system.

MitigationUpgrade Apache Fineract to version 1.11.0 or later (version 1.13.0 recommended). After upgrading, verify that the new password policy requirements are properly enforced across all user accounts.

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.11.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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 installed Apache Fineract version
    Check the Fineract version through the API endpoint /fineract-provider/api/v1/version or examine the build/configuration files in the deployment directory
    Affected if The installed version is 1.10.1 or any version prior to 1.11.0
  2. Locate password policy configuration file
    Find the application configuration file (typically fineract.yml, application.properties, or database-based configuration) that contains password policy settings
    Affected if No explicit password policy configuration exists or the password policy settings are missing entirely
  3. Verify minimum password length requirement
    Inspect the password policy configuration for a minimum length setting. Check if it is set to a weak value such as 1-4 characters or is not defined
    Affected if The minimum password length is unset, commented out, or set to less than 8 characters
  4. Check password complexity enforcement
    Review the password policy for requirements such as uppercase, lowercase, numeric, or special character enforcement. Determine if these checks are disabled or absent
    Affected if Password complexity requirements are not enforced or are explicitly disabled in the configuration
  5. Confirm password history policy
    Check if a password history or reuse prevention setting exists in the authentication configuration
    Affected if No password history policy is configured, allowing reuse of previously used passwords

Your environment is affected if Apache Fineract version is below 1.11.0 AND the password policy is either absent, weakly configured, or lacks enforcement of minimum length, complexity, or history requirements.

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.11.0 or later
Fixed in 1.11.0
Interim mitigation

Upgrade Apache Fineract to version 1.11.0 or later (version 1.13.0 recommended). After upgrading, verify that the new password policy requirements are properly enforced across all user accounts.

Recommended fix High confidence

1.13.0 (latest stable release, minimum fixed version is 1.11.0)

  1. 1. Back up the existing Fineract installation directory and database
  2. 2. Download Apache Fineract version 1.11.0 (or later, such as 1.13.0) from the official Apache Fineract distribution repository
  3. 3. Stop the currently running Fineract service
  4. 4. Replace the existing Fineract application files with the new version files
  5. 5. Run any required database migration scripts if provided in the release notes
  6. 6. Start the Fineract service
  7. 7. Verify the application is running and password requirements are now enforced

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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