CVE
Akaunting stored cross-site scripting in invoice edit form
Affects Akaunting 3.3.0 invoice import, where a user with permission to create sales invoices and import XLSX files can plant a script that runs for a second user who opens the imported invoice's edit page. No fixed version is listed.
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 is affected Attacker needs permission to create sales invoices and import XLSX invoices A second user must open the imported invoice's edit 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 contains a stored cross-site scripting flaw in its invoice edit form. An attacker with invoice-creation permission can remotely import HTML into an invoice's status field, and that markup runs in the browser of another logged-in user who opens the invoice's edit form.
Read the original description
Akaunting 3.3.0 contains a stored cross-site scripting vulnerability through invoice import. An authenticated user with invoice-creation permission can import HTML in an invoice status field. When another authenticated user opens that invoice's edit form, Akaunting renders the stored status in a hidden input with raw Blade output, allowing attacker-controlled markup to execute in the victim's Akaunting origin.
Who should check
Teams running Akaunting 3.3.0 that import invoices from XLSX files, and anyone who opens edit pages for imported invoices.
Read the source excerpt
“Akaunting 3.3.0 contains a stored cross-site scripting vulnerability in its 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 is affected Attacker needs permission to create sales invoices and import XLSX invoices A second user must open the imported invoice's edit pageWorkaround: Restrict invoice-import permission to trusted users and do not open edit pages for invoices imported from untrusted sources.
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-118855 (Akaunting 3.3.0 - Stored XSS in invoice edit form through imported status), 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-118855 (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 is affected (source: https://fluidattacks.com/advisories/sabbath)
- Attacker needs permission to create sales invoices and import XLSX invoices (source: https://fluidattacks.com/advisories/sabbath)
- A second user must open the imported invoice's edit page (source: https://fluidattacks.com/advisories/sabbath)
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 users and do not open edit pages for invoices imported from untrusted sources. (source: https://www.cve.org/CVERecord?id=CVE-2026-118855)
CISA KEV: CVE-2026-118855 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118855 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/sabbath
- https://github.com/akaunting/akaunting
- https://github.com/akaunting/akaunting/blob/3.3.0/app/Http/Requests/Document/Document.php
- https://github.com/akaunting/akaunting/blob/3.3.0/resources/views/components/form/input/hidden.blade.php
- https://www.cve.org/CVERecord?id=CVE-2026-118855
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-118855
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-118855"}.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-118855
Is CVE-2026-118855 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?
Imported invoice status values are not properly encoded, so a script stored in an imported XLSX invoice runs in the browser of a user who opens that invoice's edit page. The script runs with that user's origin and authenticated session.Source: fluidattacks.com, cve.org
Which versions are affected by CVE-2026-118855?
Akaunting: version 3.3.0.Source: cve.now feed data
Am I affected, and how do I check?
Akaunting 3.3.0 is named as affected. The bug needs a user with permission to create sales invoices who imports an XLSX invoice file, and a second user who opens the resulting invoice's edit page. Check the installed Akaunting version against 3.3.0.Source: fluidattacks.com, cve.org
How do I fix CVE-2026-118855?
The facts name no fixed version and no vendor patch ids. Until a fix is published, restrict invoice-import permission to trusted users and do not open edit pages for invoices imported from untrusted sources.Source: fluidattacks.com, cve.org
What if there's no patch?
Restrict invoice-import permission to trusted users and do not open edit pages for invoices imported from untrusted sources.Source: fluidattacks.com, cve.org