This page lists all security vulnerabilities fixed in released versions of Apache Fineract. Each vulnerability is reported via the ASF process and given a security impact rating.
If you have identified a security issue, let us know immediately via email to security AT fineract.apache.org. And be sure to secure your Fineract server!
Authorization Bypass Through User-Controlled Key vulnerability in Apache Fineract.
| Report | 2024-10-07 |
| Fix | 2025-05-16 |
| Affects | 1.11.0 and earlier releases |
Thank you Peter Chen with PayPal Security for identifying the issue. Thank you Ádám Sághy, Aleksandar Vidakovic, and Victor Romero for fixing it.
Insufficiently Protected Credentials vulnerability in Apache Fineract.
| Report | 2024-10-07 |
| Fix | 2025-04-14 |
| Affects | 1.11.0 and earlier releases |
Thank you Peter Chen with PayPal Security for identifying the issue. Thank you Jose Alberto Hernandez and Ádám Sághy for fixing it.
Weak Password Requirements vulnerability in Apache Fineract.
| Report | 2024-10-07 |
| Fix | 2024-11-11 |
| Affects | 1.10.1 and earlier releases |
Thank you Peter Chen with PayPal Security for identifying the issue. Thank you Kristof Jozsa with BaaSFlow for fixing it.
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 data into some of the REST API endpoints’ query parameter. Users are recommended to upgrade to version 1.10.1, which fixes this issue. A SQL Validator has been implemented which allows us to configure a series of tests and checks against our SQL queries that will allow us to validate and protect against nearly all potential SQL injection attacks.
| Report | 2024-04-18 |
| Fix | 2024-05-01 |
| Affects | 1.9.0 and earlier releases |
We acknowledge Kabilan S - Security engineer at Zoho, for identifying the issue and Aleksandar for resolving it.
Under certain system configurations, the sqlSearch parameter for specific endpoints was vulnerable to SQL injection attacks, potentially allowing attackers to manipulate database queries.
Fixed by https://github.com/apache/fineract/pull/3621.
| Report | 2023-09-04 |
| Fix | 2023-12-06 |
| Affects | 1.8.4 and earlier releases |
We thank Yash Sancheti of GH Solutions Consultants for reporting this issue.
Under certain system configurations, the sqlSearch parameter was vulnerable to blind SQL injection attacks, potentially allowing attackers to manipulate database queries.
Fixed by https://github.com/apache/fineract/pull/3626.
| Report | 2023-08-09 |
| Fix | 2023-12-06 |
| Affects | 1.8.4 and earlier releases |
We thank Majd Alasfar of ProgressSoft for reporting this issue.
Under certain circumstances, this vulnerability allowed users, without specific permissions, to escalate their privileges to any role, including super user status. This flaw could enable users to gain control over user management.
Fixed by https://github.com/apache/fineract/pull/3626.
| Report | 2023-09-04 |
| Fix | 2023-12-06 |
| Affects | 1.8.4 and earlier releases |
We thank Yash Sancheti of GH Solutions Consultants for reporting this issue.
Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) vulnerability in Apache Software Foundation apache fineract.
| Report | |
| Fix | |
| Affects | 1.8.3 and earlier releases |
We would like to thank Eugene Lim at Cyber Security Group (CSG) Government Technology Agency GOVTECH.sg, for reporting this issue, and the Apache Security team for their assistance. Thank you to Aleksandar Vidakovic for resolving this CVE.
Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) vulnerability in Apache Software Foundation Apache Fineract. Authorized users may be able to change or add data in certain components.
| Report | 2022-12-02 |
| Fix | 2023-03-01 |
| Affects | 1.8.3 and earlier releases |
We would like to thank Zhang Baocheng at Leng Jing Qi Cai Security Lab, for reporting this issue, and the Apache Security team for their assistance. Thank you to [email protected] for resolving this CVE.
Server-Side Request Forgery (SSRF) vulnerability in Apache Software Foundation Apache Fineract. Authorized users with limited permissions can gain access to server and may be able to use server for any outbound traffic.
| Report | 2022-12-06 |
| Fix | 2023-03-01 |
| Affects | 1.8.3 and earlier releases |
We would like to thank Huydoppa from GHTK, for reporting this issue, and the Apache Security team for their assistance. Thank you to [email protected] for resolving this CVE.
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 code. This issue affects Apache Fineract version 1.8.0 and prior versions. We recommend users to upgrade to 1.8.1.
Under typical deployments, remote code could be run.
| Report | 2022-10-31 |
| Fix | 2022-11-22 |
| Affects | 1.8.0 and earlier releases |
We would like to thank Sapra co-captain of the Super Guesser CTF team & Security researcher at CRED, for reporting this issue, and the Apache Security team for their assistance. We give kudos and karma to Aleksandar Vidakovic for resolving this CVE.
Apache Fineract disables HTTPS hostname verification in ProcessorHelper in the configureClient method.
Under typical deployments, a man in the middle attack could be successful.
| Report | 2020-10-15 |
| Fix | 2020-10-19 |
| Affects | 1.4.0 and earlier releases |
We would like to thank Simon Gerst for reporting this issue, and the Apache Security team for their assistance.
The implementation of POST with the username and password in the URL parameters exposed the credentials. More information is available in Fineract JIRA issues 726 and 629.
| Report | 2018-12-31 |
| Fix | 2020-01-01 |
| Affects | 1.3.0 and earlier releases |
We would like to thank Simon Gerst for reporting this issue, and the Apache Security team for their assistance.
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.
| Report | 2018-08-29 |
| Fix | 2018-12-01 |
| Affects | 1.2.0 and earlier releases |
We would like to thank Niels Heinen from Google for reporting this issue, and the Apache Security team for their assistance.
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.
| Report | 2018-08-29 |
| Fix | 2018-12-01 |
| Affects | 1.2.0 and earlier releases |
We would like to thank Niels Heinen from Google for reporting this issue, and the Apache Security team for their assistance.
A known vulnerability in spring security upstream dependencies allowed malicious users to trigger remote code execution.
| Report | 2018-12-17 |
| Fix | 2019-02-01 |
| Affects | 1.2.0 and earlier releases |
We would like to thank Roberto ([email protected]) for reporting this issue, and the Apache Security team for their assistance.
Within the ‘getReportType’ method, a hacker could inject SQL to read/update data for which he doesn’t have authorization for by way of the ‘reportName’ parameter.
| Report | 2018-01-23 |
| Fix | 2018-04-19 |
| Affects | 1.0.0 and earlier releases |
We would like to thank 圆珠笔 ([email protected]) and the Apache Security team for reporting this issue.
Apache Fineract exposes different REST end points to query domain specific entities with a Query Parameter ‘orderBy’ which are appended directly with SQL statements. A hacker/user can inject/draft the ‘orderBy’ query parameter by way of the “order” param in such a way to to read/update the data for which he doesn’t have authorization.
| Report | 2018-01-23 |
| Fix | 2018-04-19 |
| Affects | 1.0.0 and earlier releases |
We would like to thank 圆珠笔 ([email protected]) and the Apache Security team for reporting this issue.
Using a single quotation escape with two continuous SQL parameters can cause a SQL injection. This could be done in Methods like retrieveAuditEntries of AuditsApiResource Class retrieveCommands of MakercheckersApiResource Class
| Report | 2018-01-23 |
| Fix | 2018-04-19 |
| Affects | 1.0.0 and earlier releases |
We would like to thank 圆珠笔 ([email protected]) and the Apache Security team for reporting this issue.
Apache Fineract exposes different REST end points to query domain specific entities with a Query Parameter ‘orderBy’ and ‘sortOrder’ which are appended directly with SQL statements. A hacker/user can inject/draft the ‘orderBy’ and ‘sortOrder’ query parameter in such a way to read/update the data for which he doesn’t have authorization.
| Report | 2018-01-18 |
| Fix | 2018-04-19 |
| Affects | 1.0.0 and earlier releases |
We would like to thank 圆珠笔 ([email protected]) and the Apache Security team for reporting this issue.
An authenticated user with client/loan/center/staff/group read permissions is able to inject malicious SQL into SELECT queries. The ‘sqlSearch’ parameter on a number of endpoints is not sanitized and appended directly to the query. List of vulnerable endpoints: /staff, /clients, /loans, /centers, /groups.
| Report | 2017-04-02 |
| Fix | 2017-12-13 |
| Affects | 0.6.0-incubating and earlier releases |
We would like to thank Alex Ivanov and the Apache Security team for reporting this issue.
The source for this document is plain text with minimal Pandoc-flavor Markdown. It is rendered as HTML with Pandoc.
Keep this document simple and consistent. If you change the structure for one section, do so throughout the document.
Major headings are releases in descending order (most recent first). Minor headings are CVE ids, also in descending order. Always use www.cve.org for canonical CVE links. Date format for “Report” and “Fix” fields is YYYY-MM-DD.