Skip to main content

Apache Fineract CVE-2025-58130

CRITICAL
Insufficiently Protected Credentials (CWE-522)
2025-12-12 security@apache.org
9.1
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Fineract network endpoint
  2. Exploit
    Request insufficiently protected credential data
  3. Execution
    Recover exposed credentials
  4. Impact
    Reuse credentials to access banking data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V6 - Authentication Credential protection in transit/storage
Exploitation Conditions

The target must be a running Apache Fineract instance at or below version 1.11.0 that is network-reachable by the attacker. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, no user interaction, and no special non-default configuration are indicated as required. The practical limiting factors are: deployment scope (Fineract is typically an internal/back-office core-banking system, so exposure depends on whether the instance is reachable by the attacker rather than public-internet-facing by default) and version (fixed in 1.12.1; 1.11.0 and earlier affected). The one-line description does not name a specific feature, protocol endpoint, or configuration setting that gates the credential exposure, so the exact triggering component could not be extracted and should be confirmed from the Apache advisory thread.

Impact

Signals are moderately consistent but point to a lower real-world urgency than the 9.1 CVSS score alone suggests. The provided CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw with high confidentiality and integrity impact, which is why the base score is Critical. However, EPSS is only 0.43% (35th percentile), indicating low modeled probability of near-term exploitation, and the vulnerability is NOT in CISA KEV and has no public exploit identified at time of analysis. No SSVC decision data was provided. There is tension worth flagging: CWE-522 (Insufficiently Protected Credentials) and the 'Information Disclosure' tag most naturally map to a confidentiality loss, yet the vector asserts I:H as well - the one-line description gives no detail to confirm how integrity is affected, so the I:H rating should be verified against the Apache advisory. Net assessment: a genuinely serious design/credential-handling defect in a banking platform that warrants prompt patching due to the sensitivity of the data, but currently a patch-on-schedule priority rather than emergency, given no exploitation evidence and low EPSS.

Exploit ScenarioDerived

A remote, unauthenticated attacker interacts with an internet-reachable or internally-reachable Apache Fineract instance (version 1.11.0 or earlier) and retrieves credentials that the application stores or transmits without sufficient protection. Because the CVSS vector is AV:N/AC:L/PR:N, no special access or user interaction is needed, and the recovered credentials could then be reused to access banking/account data. No public proof-of-concept exploit code was identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Exposure of insufficiently protected credentials in Apache Fineract through 1.11.0 allows unauthenticated remote attackers who can reach an affected instance to recover credentials, resulting in high confidentiality impact; the independent assessment rates integrity and availability as not impacted. The issue is addressed in 1.12.1, with 1.13.0 recommended as the latest release. EPSS is 0.43% (35th percentile) and no public exploit identified at time of analysis.

RemediationAI

Upgrade Apache Fineract to 1.12.1 or preferably 1.13.0 per the vendor advisory; this is a vendor-released patch with 1.12.1 as the fixed version and 1.13.0 as the latest recommended release. If immediate upgrade is not possible, restrict network reachability to the Fineract instance using firewall rules, VPN, or internal segmentation because the assessed vector requires only network access and no authentication, though this may impact back-office users or integrations that depend on the service. Rotate any credentials, API keys, database passwords, or secrets that may have been exposed, and audit configurations for plaintext or weakly protected credentials, noting that rotation can disrupt dependent services until updated. Consult the advisory thread for the exact vulnerable component: https://lists.apache.org/thread/d9zpkc86zk265523tfvbr8w7gyr6onoy, and the OSS-security reference: http://www.openwall.com/lists/oss-security/2025/12/11/6.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Apache Fineract is an open-source core banking platform, and CWE-522 covers insufficiently protected credentials such as plaintext storage or transmission, weak encryption, or exposed secrets. The CPE cpe:2.3:a:apache:fineract:*:*:*:*:*:*:*:* identifies Apache Fineract as affected. The authoritative assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N indicates an unauthenticated network-reachable issue with low complexity and no user interaction, producing only confidentiality impact. The one-line description does not specify the exact endpoint, configuration file, or protocol where credentials are insufficiently protected, so the triggering component should be confirmed from the Apache advisory; NVD's 9.1 score includes integrity impact, but this synthesis follows the independent assessment limiting impact to credential disclosure.

Know when Fineract gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 7.5 HIGH

CWE-522 credential exposure over the network with no auth supports AV:N/AC:L/PR:N/C:H; I set I:N as the description gives no evidence of integrity impact, unlike the input vector's I:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Apache Fineract, the core banking platform many institutions rely on for loan, savings, and client account processing, can expose stored credentials to attackers who can reach an affected instance, putting Fineract itself and the systems it integrates with at risk of unauthorized access. Because the exposed secrets may unlock privileged application, database, or service-to-service access, leadership should treat this as a potential pathway to broader financial-system compromise rather than an isolated application defect. Only instances reachable from untrusted networks are exposed, which makes accurate inventory of internet- and partner-facing Fineract deployments the critical first step.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis per the patch-status metadata; interim mitigations are to eliminate untrusted-network exposure of Fineract instances (firewall or VPN allowlisting only), rotate all credentials and integration secrets associated with those instances, and monitor access logs for anomalous authentication or data retrieval. The vendor description references remediation in 1.12.1 with 1.13.0 recommended - validate against the current Apache advisory and deploy if confirmed available.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
niche open-source core-banking platform, limited industry-specific deployment
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:a:apache:fineract:*:*:*:*:*:*:*:*
CVE-2024-23539 CRITICAL
9.8 Mar 29

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Fineract.8.

CVE-2024-23538 CRITICAL
9.8 Mar 29

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Fineract.8.

CVE-2018-1290 CRITICAL
9.8 Apr 20

In Apache Fineract versions 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, Using a single quotation escape

CVE-2024-32838 CRITICAL
9.4 Feb 12

SQL Injection vulnerability in various API endpoints - offices, dashboards, etc. Rated critical severity (CVSS 9.4), thi

CVE-2026-35152 HIGH
8.8 Jul 15

SQL injection in Apache Fineract's Report Execution API (the runreports endpoint) in all versions up to and including 1.

CVE-2017-5663 HIGH
8.8 Dec 14

In Apache Fineract 0.4.0-incubating, 0.5.0-incubating, and 0.6.0-incubating, an authenticated user with client/loan/cent

CVE-2024-23537 HIGH
8.8 Mar 29

Improper Privilege Management vulnerability in Apache Fineract.8.5. Rated high severity (CVSS 8.8), this vulnerability i

CVE-2022-44635 HIGH
8.8 Nov 29

Apache Fineract allowed an authenticated user to perform remote code execution due to a path traversal vulnerability in

CVE-2018-1289 HIGH
8.8 Apr 20

In Apache Fineract versions 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, the system exposes different RE

CVE-2025-23408 HIGH
8.5 Dec 12

Weak password requirements in Apache Fineract through 1.10.1 allow attackers to more easily compromise user accounts via

CVE-2025-58137 HIGH
8.1 Dec 12

Authorization bypass in Apache Fineract through 1.11.0 lets an authenticated, low-privileged user access objects they sh

CVE-2026-57821 HIGH
8.1 Jul 15

SQL injection in Apache Fineract's Office Search API (GET /api/v1/offices) in all versions up to and including 1.14.0 le

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy