Quick answers
- Is CVE-2026-5568 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5568 being exploited in the wild.
- How severe is CVE-2026-5568?
- Low severity, with a CVSS score of 3.5, published 5 April 2026.
- Which products and versions are affected?
- Akaunting up to 3.1.21.
- Is there a fix for CVE-2026-5568?
- 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-5568 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-5568?
- 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 cross-site scripting (XSS) vulnerability exists in Akaunting versions up to 3.1.21 within the Invoice/Billing component. The vulnerability is caused by improper neutralization of user-supplied input in the 'notes' argument. A remote attacker with low privileges can exploit this by injecting malicious JavaScript that executes when a victim views the affected invoice. While a proof-of-concept has been disclosed, the vendor has reportedly not responded to the disclosure, and no official patch is currently confirmed.
Affected products
- Akaunting Akaunting up to 3.1.21
Timeline
- 2026-04-05: disclosed: Exploit disclosed to the public
- 2026-04-05: advisory: Vulnerability published by VulDB/NVD