What is the severity of CVE-2020-22390?

CVE-2020-22390 is classified as a high-severity vulnerability due to the potential for arbitrary code execution.

How do I fix CVE-2020-22390?

To fix CVE-2020-22390, upgrade Akaunting to version 2.1.0 or later.

What types of attacks are possible due to CVE-2020-22390?

CVE-2020-22390 allows attackers to execute arbitrary code by injecting malicious payloads into the Item name field.

In which versions of Akaunting is CVE-2020-22390 present?

CVE-2020-22390 affects Akaunting versions 2.0.9 and earlier.

What impact can CVE-2020-22390 have on users?

Users opening a compromised CSV file may unknowingly execute malicious code, leading to potential data breaches or system compromise.

Vulnerability/
CVE-2020-22390

high

8.8

CWE

1236

21/6/2021

4/8/2024

CVE-2020-22390

First published: Mon Jun 21 2021(Updated: )

Akaunting <= 2.0.9 is vulnerable to CSV injection in the Item name field, export function. Attackers can inject arbitrary code into the name parameter and perform code execution when the crafted file is opened.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Akaunting Akaunting	<=2.0.9
	<=2.0.9

Never miss a vulnerability like this again

Reference Links

https://cqinfo.la/csv-injection-in-akaunting/

Frequently Asked Questions

What is the severity of CVE-2020-22390?
CVE-2020-22390 is classified as a high-severity vulnerability due to the potential for arbitrary code execution.
How do I fix CVE-2020-22390?
To fix CVE-2020-22390, upgrade Akaunting to version 2.1.0 or later.
What types of attacks are possible due to CVE-2020-22390?
CVE-2020-22390 allows attackers to execute arbitrary code by injecting malicious payloads into the Item name field.
In which versions of Akaunting is CVE-2020-22390 present?
CVE-2020-22390 affects Akaunting versions 2.0.9 and earlier.
What impact can CVE-2020-22390 have on users?
Users opening a compromised CSV file may unknowingly execute malicious code, leading to potential data breaches or system compromise.

collector/nvd-index
agent/type
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/weakness
agent/references
agent/severity
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/tags
agent/first-publish-date
agent/event
agent/source
vendor/akaunting
canonical/akaunting akaunting
version/akaunting akaunting/2.0.9

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-22390?
CVE-2020-22390 is classified as a high-severity vulnerability due to the potential for arbitrary code execution.
How do I fix CVE-2020-22390?
To fix CVE-2020-22390, upgrade Akaunting to version 2.1.0 or later.
What types of attacks are possible due to CVE-2020-22390?
CVE-2020-22390 allows attackers to execute arbitrary code by injecting malicious payloads into the Item name field.
In which versions of Akaunting is CVE-2020-22390 present?
CVE-2020-22390 affects Akaunting versions 2.0.9 and earlier.
What impact can CVE-2020-22390 have on users?
Users opening a compromised CSV file may unknowingly execute malicious code, leading to potential data breaches or system compromise.