Quick answers
- Is CVE-2022-51019 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-51019 being exploited in the wild.
- How severe is CVE-2022-51019?
- High severity, with a CVSS score of 8.8, published 29 September 2026.
- Which products and versions are affected?
- Akaunting before 2.1.31.
- Is there a fix for CVE-2022-51019?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2022-51019 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2022-51019?
- Check whether you run Akaunting at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the module installation and update flow where the alias parameter is passed directly to shell command execution without sanitization. Authenticated admin users can inject shell metacharacters into the alias parameter to achieve OS command injection. The vulnerable code constructs a shell command string with unsanitized user input passed to Console::run(), allowing arbitrary command execution with the application's privileges.
Affected products
- Akaunting Akaunting before 2.1.31
Timeline
- 2026-09-29: disclosed