CVE-2026-5568 | Akaunting up to 3.1.21 Invoice/Billing notes cross site scripting
VulDBArchived Apr 04, 2026✓ Full text saved
A vulnerability has been found in Akaunting up to 3.1.21 and classified as problematic . This issue affects some unknown processing of the component Invoice/Billing . The manipulation of the argument notes leads to cross site scripting. This vulnerability is uniquely identified as CVE-2026-5568 . The attack is possible to be carried out remotely. Moreover, an exploit is present. The vendor was contacted early about this disclosure but did not respond in any way.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355338 · CVE-2026-5568 · GCVE-100-355338
AKAUNTING UP TO 3.1.21 INVOICE/BILLING NOTES CROSS SITE SCRIPTING
HISTORYDIFFRELATEJSONXMLCTI
Summaryinfo
A vulnerability was found in Akaunting up to 3.1.21 and classified as problematic. Impacted is an unknown function of the component Invoice/Billing. The manipulation of the argument notes results in cross site scripting. This vulnerability was named CVE-2026-5568. The attack may be performed from remote. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.
Detailsinfo
A vulnerability classified as problematic has been found in Akaunting up to 3.1.21. Affected is an unknown code of the component Invoice/Billing. The manipulation of the argument notes with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity.
The advisory is available at docs.google.com. This vulnerability is traded as CVE-2026-5568. The exploitability is told to be easy. It is possible to launch the attack remotely. Successful exploitation requires user interaction by the victim. Technical details and a public exploit are known. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The exploit is shared for download at docs.google.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Name
Akaunting
Version
3.1.0
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.1.9
3.1.10
3.1.11
3.1.12
3.1.13
3.1.14
3.1.15
3.1.16
3.1.17
3.1.18
3.1.19
3.1.20
3.1.21
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Cross site scripting
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/04/2026 Advisory disclosed
04/04/2026 +0 days VulDB entry created
04/04/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: docs.google.com
Status: Not defined
CVE: CVE-2026-5568 (🔒)
GCVE (CVE): GCVE-0-2026-5568
GCVE (VulDB): GCVE-100-355338
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 04/04/2026 16:34
Changes: 04/04/2026 16:34 (55)
Complete: 🔍
Submitter: gabriel
Cache ID: 99:F61:101
Submitinfo
Accepted
Submit #783139: Akaunting v3.1.21 Cross Site Scripting (by gabriel)
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸