CVE
Akaunting stored XSS in custom invoice payment terms
Only affects Akaunting 3.3.0 when a non-predefined custom invoice payment-term value is saved in company invoice settings. No fixed version is named.
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 A non-predefined custom payment-term value must be saved in the company's invoice settings Another authenticated user in the same company, such as an Administrator, opens Invoice Settings
- 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 custom invoice payment terms. An attacker with Manager-level login can save a crafted payment term over the network, and the script runs in another authorized user's session when that user opens Invoice Settings for the same company.
Read the original description
Akaunting 3.3.0 contains a stored cross-site scripting vulnerability in custom invoice payment terms. An authenticated Manager can save a crafted custom payment-term value. When an authorized user opens Invoice Settings for the same company, Akaunting inserts the stored value into a client-side event-handler expression, causing attacker-controlled JavaScript to execute in the victim's authenticated origin.
Who should check
Teams running Akaunting 3.3.0 where users with the Manager role can edit Invoice Settings and Administrators open those settings.
Not fixed by: Workaround measures reduce exposure but do not correct the unsafe sink.
Read the source excerpt
“Akaunting 3.3.0 contains a stored cross-site scripting vulnerability”
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.2/10CVSS 7.2
- 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 A non-predefined custom payment-term value must be saved in the company's invoice settings Another authenticated user in the same company, such as an Administrator, opens Invoice SettingsWorkaround: Replace custom invoice.payment_terms values with predefined numeric options and restrict settings-invoice update access to trusted users.
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-118597 (Akaunting 3.3.0 - Stored XSS in custom invoice payment terms), 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-118597 (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/rhiannon)
- A non-predefined custom payment-term value must be saved in the company's invoice settings (source: https://fluidattacks.com/advisories/rhiannon)
- Another authenticated user in the same company, such as an Administrator, opens Invoice Settings (source: https://fluidattacks.com/advisories/rhiannon)
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: Replace custom invoice.payment_terms values with predefined numeric options and restrict settings-invoice update access to trusted users. (source: https://fluidattacks.com/advisories/rhiannon)
CISA KEV: CVE-2026-118597 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118597 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/rhiannon
- https://github.com/akaunting/akaunting
- https://github.com/akaunting/akaunting/blob/3.3.0/app/View/Components/Form/Group/PaymentTerm.php
- https://github.com/akaunting/akaunting/blob/3.3.0/resources/views/components/form/group/payment_term.blade.php
- https://github.com/akaunting/akaunting/blob/3.3.0/app/Abstracts/Http/SettingController.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-118597
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-118597"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Akaunting Akaunting
3.3.0
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Repository
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118597
Is CVE-2026-118597 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 custom invoice payment-terms value saved in the company's invoice settings can run JavaScript when another signed-in user in the same company, such as an Administrator, opens Invoice Settings. The script runs in that user's session, so it can read application data exposed to that session and invoke authenticated actions such as user management.Source: fluidattacks.com
Which versions are affected by CVE-2026-118597?
Akaunting: version 3.3.0.Source: cve.now feed data
Am I affected, and how do I check?
Akaunting 3.3.0 is affected. To check an installation, confirm the installed Akaunting version and whether the invoice payment-terms setting holds a custom value rather than one of the predefined numeric options.Source: fluidattacks.com
How do I fix CVE-2026-118597?
The advisory does not name a fixed version or patch, so no upgrade target is given. Apply the workaround until a fixed release is available.Source: fluidattacks.com
What if there's no patch?
Replace custom invoice.payment_terms values with predefined numeric options. Restrict settings-invoice update access to trusted users.Source: fluidattacks.com