Skip to main content
VulnerabilityPublished

CVE-2026-40524: FA · FrontAccounting versions before 2.4.20 have a SQL injection vulnerability in the get_gl_transactions() function

Affects FASource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 2.4.20 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade frontaccountingerp/FA to 2.4.20.

Affected software

ProductAffectedFixed in
GitHubfrontaccountingerp/FApkg:github/frontaccountingerp/FAOther threatsAffected
  • <2.4.20
Fixed in
  • 2.4.20

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, 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.

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.

References

Community reviews

Loading reviews…