Security readout for executives and security teams
Plain-English summary
Akaunting 2.1.12 and earlier allowed a logged-in user to bypass company-selection authorization through a user-controlled companies[0] field. For an accounting system, that can expose or alter sensitive company financial data. The issue is high severity and was fixed in Akaunting 2.1.13.
Executive priority
Prioritize remediation for any production Akaunting system because accounting data has high business sensitivity. If the system is internet-facing or supports many user accounts, treat upgrade validation as a near-term operational priority.
Technical view
CVE-2021-36801 is an authentication/authorization bypass mapped to CWE-639. The CVSS 3.1 score is 8.1: network exploitable, low complexity, low privileges required, no user interaction, with high confidentiality and integrity impact. The source bundle identifies Akaunting 2.1.12 and earlier as affected and 2.1.13 as fixed.
Likely exposure
Organizations running Akaunting 2.1.12 or earlier are exposed, especially internet-accessible installations with multiple users or company records. The CVSS vector requires low privileges, so risk is highest where ordinary user accounts exist or can be obtained.
Exploitation context
The provided data does not show CISA KEV listing or active exploitation. Public evidence supports a serious authorization flaw but does not establish exploitation in the wild. Treat as urgent because compromise could affect accounting confidentiality and integrity.
Researcher notes
The key evidence is limited to the CVE description, CVSS vector, CWE-639 classification, affected version statement, and Rapid7 reference. The bundle identifies the problematic companies[0] field but does not provide safe vendor test cases or detailed advisory mitigations beyond the fixed version.
Mitigation direction
- Upgrade Akaunting to version 2.1.13 or later.
- Inventory all Akaunting deployments and confirm installed versions.
- Restrict access to Akaunting until affected instances are upgraded.
- Review company memberships and user permissions for unexpected access.
- Check vendor guidance for any additional hardening or backport advice.
Validation and detection
- Confirm each Akaunting instance reports version 2.1.13 or later.
- Verify no production instance remains on 2.1.12 or earlier.
- Review application access logs for unusual cross-company access patterns.
- Confirm user accounts have only expected company assignments.
- Document patch status and any temporary access restrictions.
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.
CWE-639: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-36801 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
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.rapid7.com/blog/post/2021/07/27/multiple-open-source-web-app-vulnerabilities-fixed/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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.