Akaunting 3.3.0 - Stored XSS through imported item names
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Akaunting | Akaunting | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Akaunting | Akaunting |
|
Vendor Solution
Apply an upstream patch that treats imported item names as untrusted text in every write path, and replace the document line item's v-html rendering with a text-only Vue binding. Upgrade to the vendor-fixed release once one is published.
Vendor Workaround
Restrict item-import permission to trusted administrators, review existing item names for markup, and avoid selecting untrusted imported items until a vendor fix is available.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.425% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Akaunting 3.3.0 contains a stored cross-site scripting vulnerability in the XLSX item-import workflow. An authenticated Manager can import an item whose name contains HTML. When another authenticated user selects that item while creating a document, Akaunting places the stored name in an invoice or bill line item through Vue v-html, causing attacker-controlled markup to execute in the victim's Akaunting origin. | |
| Title | Akaunting 3.3.0 - Stored XSS through imported item names | |
| First Time appeared |
Akaunting
Akaunting akaunting |
|
| Weaknesses | CWE-79 | |
| CPEs | cpe:2.3:a:akaunting:akaunting:3.3.0:*:linux:*:*:*:*:* cpe:2.3:a:akaunting:akaunting:3.3.0:*:macos:*:*:*:*:* cpe:2.3:a:akaunting:akaunting:3.3.0:*:windows:*:*:*:*:* |
|
| Vendors & Products |
Akaunting
Akaunting akaunting |
|
| References |
| |
| Metrics |
cvssV4_0
|