Quick answers
- Is CVE-2026-118368 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118368 being exploited in the wild.
- How severe is CVE-2026-118368?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Akaunting 3.3.0.
- Is there a fix for CVE-2026-118368?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-118368 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-118368?
- Check whether you run Akaunting at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Stored XSS vulnerability in the XLSX item-import workflow where unsanitized item names are rendered via Vue v-html directive. An authenticated Manager can import an item with HTML payload in its name; when another authenticated user selects that item during document creation, the markup executes in their browser within the Akaunting origin, bypassing CSP or output encoding.
Affected products
- Akaunting Akaunting 3.3.0
Timeline
- 2026-11-11: disclosed