LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36805: Akaunting Invoice Footer Persistent XSS

Akaunting version 2.1.12 and earlier suffers from a persistent (type II) cross-site scripting (XSS) vulnerability in the sales invoice processing component of the application. This issue was fixed in version 2.1.13 of the product.

MediumCVSS 5.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Akaunting 2.1.12 and earlier had a stored cross-site scripting flaw in invoice footer handling. A highly privileged user could save hostile content that later runs when another user views the affected invoice area. This is not listed as actively exploited in the provided sources, but it can threaten sensitive business data in billing workflows.

Executive priority

Treat as a moderate-priority remediation for finance systems. Patch promptly during the normal maintenance window, sooner for internet-facing deployments or environments with weak administrative account controls.

Technical view

CVE-2021-36805 is CWE-79 persistent XSS in Akaunting sales invoice processing, specifically invoice footer content. CVSS 3.1 is 5.2: network reachable, low complexity, high privileges required, user interaction required, unchanged scope, high confidentiality impact, low integrity impact, no availability impact. The issue is reported fixed in Akaunting 2.1.13.

Likely exposure

Exposure is limited to organizations running Akaunting 2.1.12 or earlier, especially self-hosted or internet-accessible deployments where privileged users can edit invoice footer content and other users view invoices.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation requires high privileges and user interaction, reducing broad attack likelihood but still creating risk if an admin account is misused or compromised.

Researcher notes

Evidence is narrow: the bundle identifies Akaunting 2.1.12 and earlier, CWE-79, CVSS details, and a fixed version. No CPEs, exploit indicators, or broader product impacts are provided, so validation should focus on confirmed Akaunting deployments only.

Mitigation direction

  • Upgrade Akaunting to version 2.1.13 or later.
  • Review Akaunting vendor guidance for any related security instructions.
  • Restrict invoice customization privileges to trusted administrative users.
  • Review existing invoice footer content for unexpected active content.
  • Monitor billing application accounts for suspicious privileged changes.

Validation and detection

  • Inventory all Akaunting deployments and record exact versions.
  • Confirm production instances are no longer running 2.1.12 or earlier.
  • Identify who can edit invoice footer or sales invoice templates.
  • Review recent invoice footer changes for unauthorized content.
  • Confirm rendered invoice views encode or neutralize footer content.
Prepared
Confidence
high
Sources
3

Public sources used

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 · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-36805 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
5.2 (3.1)
Known Exploited
No
Published

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

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
5.2CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N0.94.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.