FrontAccounting < 2.4.20 SQL Injection via get_gl_transactions()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| FrontAccounting | FrontAccounting | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Frontaccounting | Frontaccounting |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.345% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:frontaccounting:frontaccounting:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Frontaccounting
Frontaccounting frontaccounting |
|
| Vendors & Products |
Frontaccounting
Frontaccounting frontaccounting |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FrontAccounting before 2.4.20 contains a SQL injection vulnerability in the get_gl_transactions() function where the filter_type parameter is concatenated directly into a SQL IN() clause without parameterization. Attackers with SA_GLANALYTIC permission can inject arbitrary SQL by supplying a closing parenthesis followed by malicious conditions to extract sensitive journal entry data through boolean-based blind SQL injection with reliable response size differentials. | |
| Title | FrontAccounting < 2.4.20 SQL Injection via get_gl_transactions() | |
| Weaknesses | CWE-89 | |
| References |
|
|
| Metrics |
cvssV3_1
|