Quick answers
- Is CVE-2026-118855 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118855 being exploited in the wild.
- How severe is CVE-2026-118855?
- Informational severity, published 12 November 2026.
- Which products and versions are affected?
- Akaunting 3.3.0.
- Is there a fix for CVE-2026-118855?
- 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-118855 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118855?
- 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
A stored XSS vulnerability exists in Akaunting 3.3.0's invoice import functionality. An authenticated user with invoice-creation permission can inject HTML/JavaScript into the invoice status field. When a second authenticated user opens the invoice's edit form, the application renders the status field in a hidden input using raw Blade templating output without sanitization, allowing attacker-controlled markup to execute in the victim's browser within the Akaunting origin.
Affected products
- Akaunting Akaunting 3.3.0
Timeline
- 2026-11-12: disclosed