Apache Fineract vulnerabilities
23 CVEs affecting Apache Fineract, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-57821, published 2026-07-15.
More from Apache.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2022-44635, published 2022-11-29. High severity, CVSS 8.8. EPSS: 68.8% chance of exploitation in the next 30 days. Apache Fineract allowed an authenticated user to perform remote code execution due to a path traversal vulnerability in a file upload component of Apache Fineract, allowing an attacker to run remote…
- CVE-2018-11801, published 2019-06-11. Critical severity, CVSS 9.8. EPSS: 5.2% chance of exploitation in the next 30 days. SQL injection vulnerability in Apache Fineract before 1.3.0 allows attackers to execute arbitrary SQL commands via a query on a m_center data related table.
- CVE-2018-11800, published 2019-06-11. Critical severity, CVSS 9.8. EPSS: 5.2% chance of exploitation in the next 30 days. SQL injection vulnerability in Apache Fineract before 1.3.0 allows attackers to execute arbitrary SQL commands via a query on the GroupSummaryCounts related table.
- CVE-2020-17514, published 2021-05-27. High severity, CVSS 7.4. EPSS: 3.4% chance of exploitation in the next 30 days. Apache Fineract prior to 1.5.0 disables HTTPS hostname verification in ProcessorHelper in the configureClient method. Under typical deployments, a man in the middle attack could be successful.
- CVE-2026-35152, published 2026-07-15. High severity, CVSS 8.8. EPSS: 3.3% chance of exploitation in the next 30 days. 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…
- CVE-2018-1290, published 2018-04-20. Critical severity, CVSS 9.8. EPSS: 3.2% chance of exploitation in the next 30 days. In Apache Fineract versions 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, Using a single quotation escape with two continuous SQL parameters can cause a SQL injection. This could be…
- CVE-2018-20243, published 2020-10-13. High severity, CVSS 7.5. EPSS: 2.7% chance of exploitation in the next 30 days. The implementation of POST with the username and password in the URL parameters exposed the credentials. More infomration is available in fineract jira issues 726 and 629.
- CVE-2018-1289, published 2018-04-20. High severity, CVSS 8.8. EPSS: 2.5% chance of exploitation in the next 30 days. In Apache Fineract versions 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, the system exposes different REST end points to query domain specific entities with a Query Parameter…
- CVE-2017-5663, published 2017-12-14. High severity, CVSS 8.8. EPSS: 2.1% chance of exploitation in the next 30 days. In Apache Fineract 0.4.0-incubating, 0.5.0-incubating, and 0.6.0-incubating, an authenticated user with client/loan/center/staff/group read permissions is able to inject malicious SQL into SELECT…
- CVE-2018-1292, published 2018-04-20. High severity, CVSS 8.1. EPSS: 2% chance of exploitation in the next 30 days. Within the 'getReportType' method in Apache Fineract 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, a hacker could inject SQL to read/update data for which he doesn't have authorization…
Latest
- CVE-2026-57821, published 2026-07-15. High severity, CVSS 8.1. EPSS: 0.7% chance of exploitation in the next 30 days. A SQL Injection vulnerability exists in Apache Fineract's Office Search API (GET /api/v1/offices) in versions up to and including 1.14.0. The orderBy request parameter is concatenated into a SQL…
- CVE-2026-56287, published 2026-07-15. High severity, CVSS 8.1. EPSS: 0.7% chance of exploitation in the next 30 days. A boolean-based SQL Injection vulnerability exists in Apache Fineract's Client Search API (GET /api/v1/clients) in versions up to and including 1.14.0. The orderBy and sortOrder request parameters…
- CVE-2025-58137, published 2025-12-12. High severity, CVSS 8.1. EPSS: 0.4% chance of exploitation in the next 30 days. 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…
- CVE-2025-58130, published 2025-12-12. Critical severity, CVSS 9.1. EPSS: 0.4% chance of exploitation in the next 30 days. 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…
- CVE-2025-23408, published 2025-12-12. Medium severity, CVSS 6.5. EPSS: 0.5% chance of exploitation in the next 30 days. 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…
- CVE-2024-32838, published 2025-02-12. High severity, CVSS 8.8. EPSS: 1.5% chance of exploitation in the next 30 days. SQL Injection vulnerability in various API endpoints - offices, dashboards, etc. Apache Fineract versions 1.9 and before have a vulnerability that allows an authenticated attacker to inject malicious…
- CVE-2024-23539, published 2024-03-29. Critical severity, CVSS 9.8. EPSS: 1.5% chance of exploitation in the next 30 days. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Fineract.This issue affects Apache Fineract: <1.8.5. Users are recommended to upgrade to…
- CVE-2024-23538, published 2024-03-29. Critical severity, CVSS 9.8. EPSS: 1.3% chance of exploitation in the next 30 days. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Fineract.This issue affects Apache Fineract: <1.8.5. Users are recommended to upgrade to…
- CVE-2024-23537, published 2024-03-29. High severity, CVSS 8.8. EPSS: 1.1% chance of exploitation in the next 30 days. Improper Privilege Management vulnerability in Apache Fineract.This issue affects Apache Fineract: <1.8.5. Users are recommended to upgrade to version 1.9.0, which fixes the issue.