dbcve.org
AkauntingApplication

CVE-2024-22836

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to 3.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OS command injection vulnerability in Akaunting v3.1.3 and earlier allowing remote code execution through manipulation of the company locale parameter during application installation.

MitigationUpgrade to patched version; if no patch available, audit and sanitize all user inputs in installation routines that interact with system commands, implement input validation, and use parameterized execution methods instead of shell commands.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AkauntingApplication
Affected:< 3.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Akaunting version
    Locate the version file or check the admin panel for the current Akaunting version number
    Affected if Version is 3.1.3 or earlier (anything below 3.1.4)
  2. Check if installation directory exists
    Inspect the server filesystem for the presence of the /install route or installation folder (such as /install, /setup, or the installer PHP files)
    Affected if Installation files remain accessible on the server (the vulnerability is exploited during the installation process)
  3. Determine if installation has been completed
    Look for a flag or configuration file indicating installation is finished (such as a .env file with APP_INSTALLED=true or similar marker)
    Affected if Installation has not been completed or can be re-run - the flaw is only exploitable during the installation routine when the company locale parameter is set
  4. Verify installation endpoint accessibility
    Attempt to access the installation route via HTTP request or check web server configuration for routes exposing the installer
    Affected if The installation endpoint is reachable without authentication and the application has not been locked down post-install

You are affected if Akaunting version is below 3.1.4 AND the installation routine (or re-installation capability) remains accessible, since the command injection occurs through the company locale parameter during installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.4 or later
Fixed in 3.1.4
Interim mitigation

Upgrade to patched version; if no patch available, audit and sanitize all user inputs in installation routines that interact with system commands, implement input validation, and use parameterized execution methods instead of shell commands.

Recommended fix High confidence

Akaunting 3.1.4 or later

  1. 1. Back up your existing Akaunting database and files before any upgrade
  2. 2. Download Akaunting version 3.1.4 or the latest stable release from the official Akaunting website (akaunting.com) or GitHub repository
  3. 3. Replace the existing Akaunting installation files with the new version
  4. 4. Run any available database migration scripts if included in the upgrade
  5. 5. Verify the upgrade was successful by checking the application version in the admin panel
  6. 6. Test critical functionality to ensure the application works correctly after the upgrade
Caveat Review the official release notes for version 3.1.4 to check for any breaking changes or required configuration updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Akaunting Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22836 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22836 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data