Security readout for executives and security teams
Plain-English summary
Akaunting versions up to 2.0.9 can place attacker-controlled item names into exported CSV files in a dangerous way. The main risk appears when a staff member opens a crafted export in a spreadsheet application, which may execute embedded spreadsheet formula behavior.
Executive priority
Treat this as a targeted operational risk, not a broad internet remote takeover. Prioritize if external customers or low-trust users can influence item records and finance or admin staff routinely open exports.
Technical view
The source describes CSV injection in Akaunting <= 2.0.9 through the Item name field and export function. The CVE record provides no CVSS, CWE, CPE, or confirmed fixed version. Exploitation depends on attacker influence over item names and a downstream user opening the exported CSV.
Likely exposure
Exposure is likely limited to Akaunting deployments at or below 2.0.9 where untrusted users can create or modify item names and staff export those records to CSV.
Exploitation context
The bundle does not show active exploitation, and KEV is false. The issue is a workflow-dependent client-side risk: the malicious content becomes dangerous when a generated CSV is opened by a user in spreadsheet software.
Researcher notes
Evidence is sparse. The CVE entry names Akaunting <= 2.0.9 and the Item name export path, but lacks CVSS, CWE, CPE, and patch metadata. Do not claim exploitation or a fixed version without additional vendor confirmation.
Mitigation direction
- Check Akaunting vendor guidance for the fixed version or recommended workaround.
- Upgrade from Akaunting <= 2.0.9 if vendor guidance confirms a patched release.
- Restrict who can create or modify item names until remediation is complete.
- Warn staff not to open untrusted exports in spreadsheet applications.
- Review export handling for neutralization of formula-like CSV cell content.
Validation and detection
- Confirm whether any Akaunting instance is running version 2.0.9 or earlier.
- Identify roles that can control Item name values.
- Review whether CSV exports encode or neutralize risky spreadsheet-leading characters.
- Check business workflows where exported item CSV files are opened by staff.
- Document whether vendor guidance names a fixed release or workaround.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-22390 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://cqinfo.la/csv-injection-in-akaunting/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.