Secuno
ENNL
Book demo

CVE-2024-22836

Akaunting command injection

9.8 CRITICALEPSS 30.0%
  1. Published8 Feb 2024

Description

An OS command injection vulnerability exists in Akaunting v3.1.3 and earlier. An attacker can manipulate the company locale when installing an app to execute system commands on the hosting server.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Akaunting< 3.1.4

Remediation

Fixed in
Akaunting≥ 3.1.4

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-185298.7
IBM Maximo Application Suite - Location Service for Esri Component 9.2, 9.1, and 9.0 is…
CVE-2025-714299.8
GPT-SoVITS through 20250606v2pro contains an OS command injection vulnerability in…
CVE-2020-372798.1
easy-pdf-merge 0.1.0 through 0.2.6 contains an OS command injection vulnerability that…
CVE-2026-1093188.8
Grav Git Sync 1.0.2 through 3.4.12 contains a command injection vulnerability that…
CVE-2026-1088969.9
A vulnerability was found in Linksys E1700 1.0.0.4.003. This affects the function…
CVE-2026-1088959.9
A weakness has been identified in Linksys E1700 1.0.0.4.003. The affected element is…

Frequently asked

Is CVE-2024-22836 being actively exploited?

CVE-2024-22836 is not in the CISA KEV catalog. Its EPSS exploit probability is 30.0%.

How severe is CVE-2024-22836?

CVE-2024-22836 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 30.0% probability of exploitation.

Which products are affected by CVE-2024-22836?

Affected products include Akaunting.

How do I fix CVE-2024-22836?

Upgrade affected software to a fixed version, for example Akaunting 3.1.4 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-22836 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.