LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36802: Akaunting DoS via User-Controlled 'locale' Variable

Akaunting version 2.1.12 and earlier suffers from a denial-of-service issue that is triggered by setting a malformed 'locale' variable and sending it in an otherwise normal HTTP POST request. This issue was fixed in version 2.1.13 of the product.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Akaunting 2.1.12 and earlier can be forced into a denial-of-service condition through malformed locale input in a normal HTTP POST request. The issue affects availability, not data confidentiality or integrity, and was fixed in Akaunting 2.1.13.

Executive priority

Treat this as a moderate availability risk. Prioritize remediation for internet-facing or business-critical Akaunting systems, but it is less urgent than flaws enabling data theft, privilege escalation, or confirmed active exploitation.

Technical view

The CVE describes improper handling of a user-controlled locale value, mapped to CWE-248, causing a denial-of-service condition. CVSS 3.1 is 6.5: network reachable, low complexity, low privileges required, no user interaction, high availability impact, and no confidentiality or integrity impact.

Likely exposure

Exposure is most likely in Akaunting deployments at version 2.1.12 or earlier, especially internet-facing instances where authenticated users can submit affected POST requests. The bundle does not identify specific hosted services, plugins, or configurations beyond Akaunting itself.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Rapid7 publicly disclosed multiple open-source web application vulnerabilities, but the provided sources do not establish exploitation in the wild for this CVE.

Researcher notes

Validation should focus on version confirmation, reachable authenticated POST surfaces, and evidence of locale-handling exceptions. Do not assume unauthenticated exposure: the CVSS vector indicates low privileges are required. Sources identify the fix version but provide limited operational detail.

Mitigation direction

  • Upgrade Akaunting to version 2.1.13 or later.
  • Check Akaunting vendor guidance for any additional supported remediation.
  • Restrict access to Akaunting administration and authenticated workflows where feasible.
  • Monitor application errors and availability metrics for abnormal locale-related failures.

Validation and detection

  • Inventory all Akaunting instances and confirm their exact version.
  • Verify no production instance remains on 2.1.12 or earlier.
  • Review logs for repeated locale-related exceptions or availability errors.
  • Confirm the upgrade in staging before production rollout.
  • Avoid malformed-input testing in production unless formally approved.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · low confidence lookup

CWE-248: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-36802 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-36802Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AkauntingAkaunting2.1.12Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-248 · source CWE mapping

Uncaught Exception

Uncaught Exception represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.