Quick answers
- Is CVE-2026-11943 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11943 being exploited in the wild.
- How severe is CVE-2026-11943?
- Informational severity, with a CVSS score of 4.8, published 22 June 2026.
- Which products and versions are affected?
- Akaunting 3.1.21.
- Is there a fix for CVE-2026-11943?
- 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-11943 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-11943?
- 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 version 3.1.21 due to improper neutralization of input in the user profile name field. An authenticated attacker with high privileges can inject malicious HTML or JavaScript into their profile name. This payload is subsequently executed in the context of other users' browsers when they navigate to the document timeline on invoice or bill detail pages. The vulnerability is tracked as CWE-79 and requires user interaction (viewing the affected page) to trigger the execution of the stored script.
Affected products
- Akaunting Akaunting 3.1.21
Timeline
- 2026-06-22: disclosed
- 2026-06-22: advisory