CVE
Akaunting stored XSS in XLSX invoice import
Only affects Akaunting 3.3.0 when invoices are imported from XLSX files and linked to recurring invoices, and a victim opens the affected recurring invoice page. CVSS scores it 7 (high). The checked facts name no fixed version or patch ids.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Akaunting 3.3.0 An imported ordinary invoice is linked to a recurring invoice as its child A victim opens the affected recurring invoice detail page
- 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
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.30% · 22nd percentile
- 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 3.3.0 has a stored cross-site scripting flaw in its XLSX invoice-import feature: an attacker with a Manager account can import an invoice whose number contains HTML, and it runs in another user's browser when that user opens the linked recurring invoice. The attack is reached remotely over the network, but it requires the attacker to be logged in with Manager privileges and a victim to open the affected recurring invoice.
Read the original description
Akaunting 3.3.0 contains a stored cross-site scripting vulnerability in the XLSX invoice-import workflow. An authenticated Manager can import a child invoice whose invoice number contains HTML and is linked to a recurring invoice. When a victim opens that recurring invoice, Akaunting raw-renders the stored child number in an anchor, causing attacker-controlled markup to execute in the victim's browser.
Who should check
Teams running Akaunting 3.3.0 that let users import invoices from XLSX workbooks and use recurring invoices.
Read the source excerpt
“Akaunting 3.3.0 contains a stored XSS vulnerability in the XLSX invoice-import workflow.”
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
Check whether your setup matches what the bug needs.
Akaunting 3.3.0 An imported ordinary invoice is linked to a recurring invoice as its child A victim opens the affected recurring invoice detail pageWorkaround: Restrict invoice-import permission to trusted administrators, inspect existing document numbers for markup, and avoid opening recurring invoices with children imported from untrusted workbooks.
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-119275 (Akaunting 3.3.0 - Stored XSS through imported invoice numbers), 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-119275 (entry last updated 2026-11-12):
Affected:
- Akaunting Akaunting: versions 3.3.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Akaunting 3.3.0 (source: https://fluidattacks.com/advisories/soda)
- An imported ordinary invoice is linked to a recurring invoice as its child (source: https://fluidattacks.com/advisories/soda)
- A victim opens the affected recurring invoice detail page (source: https://fluidattacks.com/advisories/soda)
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 invoice-import permission to trusted administrators, inspect existing document numbers for markup, and avoid opening recurring invoices with children imported from untrusted workbooks. (source: https://fluidattacks.com/advisories/soda)
CISA KEV: CVE-2026-119275 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119275 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/advisories/soda
- https://github.com/akaunting/akaunting
- https://github.com/akaunting/akaunting/blob/3.3.0/app/Imports/Sales/Invoices/Sheets/Invoices.php
- https://github.com/akaunting/akaunting/blob/3.3.0/resources/views/components/documents/show/children.blade.php
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-119275
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119275"}.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-119275
Is CVE-2026-119275 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
What does this mean?
A document number in an imported XLSX invoice can contain markup that is inserted unescaped into the child link of a recurring invoice. When an authenticated victim opens that recurring invoice detail page, attacker-controlled JavaScript runs in their Akaunting session and can read data exposed to the browser and submit same-origin actions the victim is authorized to perform.Source: fluidattacks.com
Which versions are affected by CVE-2026-119275?
Akaunting: version 3.3.0.Source: cve.now feed data
Am I affected, and how do I check?
The advisory names Akaunting 3.3.0 and an ordinary invoice imported through the XLSX invoice-import workflow and linked to a recurring invoice as its child. Check whether the installed Akaunting version is 3.3.0; no other versions are named in the checked facts.Source: fluidattacks.com
How do I fix CVE-2026-119275?
The checked facts name no fixed version or vendor patch ids. The advisory's remedy is to escape document_number when constructing the child link and to avoid passing a prebuilt HTML string to a raw translation sink.Source: fluidattacks.com
What if there's no patch?
Restrict invoice-import permission to trusted administrators, inspect existing document numbers for markup, and avoid opening recurring invoices with children imported from untrusted workbooks.Source: fluidattacks.com