Akaunting 3.3.0 - Stored XSS through imported item names
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Workaround: Restrict item-import permission to trusted administrators, review existing item names for markup, and avoid selecting untrusted imported items until a vendor fix is available.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Akaunting has a stored cross-site scripting flaw in its XLSX item-import workflow that lets an attacker run malicious script in another user's Akaunting session. An attacker who can log in with high privileges, such as a Manager account, can reach it remotely over the network by importing an item whose name contains HTML, and the script runs when another user selects that item while creating an invoice or bill.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Akaunting 3.3.0 contains a stored cross-site scripting vulnerability in the XLSX item-import workflow. An authenticated Manager can import an item whose name contains HTML. When another authenticated user selects that item while creating a document, Akaunting places the stored name in an invoice or bill line item through Vue v-html, causing attacker-controlled markup to execute in the victim's Akaunting origin.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7/10CVSS 7.0
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Workaround: Restrict item-import permission to trusted administrators, review existing item names for markup, and avoid selecting untrusted imported items until a vendor fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-118368 (Akaunting 3.3.0 - Stored XSS through imported item names), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-118368 (entry last updated 2026-11-11): Affected: - Akaunting Akaunting: versions 3.3.0 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, high-privilege login, a user action. Workaround: Restrict item-import permission to trusted administrators, review existing item names for markup, and avoid selecting untrusted imported items until a vendor fix is available. (source: https://www.cve.org/CVERecord?id=CVE-2026-118368) CISA KEV: CVE-2026-118368 is not listed as of cve.now's last read. This KEV status is for CVE-2026-118368 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://fluidattacks.com/es/advisories/tool - https://github.com/akaunting/akaunting - https://github.com/akaunting/akaunting/blob/3.3.0/app/Imports/Common/Sheets/Items.php - https://github.com/akaunting/akaunting/blob/3.3.0/resources/views/components/documents/form/line-item.blade.php - https://www.cve.org/CVERecord?id=CVE-2026-118368 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-118368 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-118368.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Akaunting Akaunting
3.3.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118368
Is CVE-2026-118368 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-118368?
Akaunting: version 3.3.0.Source: cve.now feed data
How do I fix CVE-2026-118368?
No fixed release is listed in the checked facts. The advisory says to upgrade to the vendor-fixed release once one is published.Source: cve.org
What if there's no patch?
Restrict item-import permission to trusted administrators and review existing item names for markup. Avoid selecting untrusted imported items until a vendor fix is available.Source: cve.org