GHSA-w5j4-x499-pfwp
FrontAccounting versions before 2.4.20 have a SQL injection vulnerability in the get_gl_transactions() function. The vulnerability arises because the filter_type parameter is directly concatenated into a SQL IN() clause without proper parameterization. Attackers with SA_GLANALYTIC permission can exploit this to perform boolean-based blind SQL injection, potentially extracting sensitive journal entry data.
AI Analysis
Technical Summary
The vulnerability in FrontAccounting prior to version 2.4.20 is a SQL injection flaw located in the get_gl_transactions() function. Specifically, the filter_type parameter is concatenated directly into a SQL IN() clause without parameterization, allowing attackers with SA_GLANALYTIC permission to inject arbitrary SQL. This injection can be exploited using a closing parenthesis followed by malicious conditions, enabling boolean-based blind SQL injection attacks that can reliably extract sensitive journal entry data by observing response size differences.
Potential Impact
An attacker with SA_GLANALYTIC permission can exploit this vulnerability to perform SQL injection attacks, potentially extracting sensitive financial journal entry data from the database. This could lead to unauthorized disclosure of sensitive accounting information. There is no indication of privilege escalation or remote code execution from the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict SA_GLANALYTIC permissions to trusted users only and monitor for suspicious activity related to the get_gl_transactions() function. Avoid using vulnerable versions of FrontAccounting in untrusted environments.
GHSA-w5j4-x499-pfwp
Description
FrontAccounting versions before 2.4.20 have a SQL injection vulnerability in the get_gl_transactions() function. The vulnerability arises because the filter_type parameter is directly concatenated into a SQL IN() clause without proper parameterization. Attackers with SA_GLANALYTIC permission can exploit this to perform boolean-based blind SQL injection, potentially extracting sensitive journal entry data.
CVSS v4.0
Affected software
pkg:github/frontaccountingerp/FARun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in FrontAccounting prior to version 2.4.20 is a SQL injection flaw located in the get_gl_transactions() function. Specifically, the filter_type parameter is concatenated directly into a SQL IN() clause without parameterization, allowing attackers with SA_GLANALYTIC permission to inject arbitrary SQL. This injection can be exploited using a closing parenthesis followed by malicious conditions, enabling boolean-based blind SQL injection attacks that can reliably extract sensitive journal entry data by observing response size differences.
Potential Impact
An attacker with SA_GLANALYTIC permission can exploit this vulnerability to perform SQL injection attacks, potentially extracting sensitive financial journal entry data from the database. This could lead to unauthorized disclosure of sensitive accounting information. There is no indication of privilege escalation or remote code execution from the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict SA_GLANALYTIC permissions to trusted users only and monitor for suspicious activity related to the get_gl_transactions() function. Avoid using vulnerable versions of FrontAccounting in untrusted environments.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w5j4-x499-pfwp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-40524"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a42ed4f27e9c79719936058
Added to database: 06/29/2026, 22:10:23 UTC
Last enriched: 06/29/2026, 22:28:44 UTC
Last updated: 06/30/2026, 00:46:01 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.