Finding and attribution
Akaunting 3.3.0 can expose another user in the same company to script execution through stored invoice payment settings. A Manager account is required; administrative consequences depend on the affected user's existing privileges. The individual advisory attributes detection to Fluid Attacks' AI SAST Scanner and disclosure to Miguel Gómez.
What to update · Akaunting
Affected versions not confirmed in this summary.
Remediation note: The individual advisory describes temporary restrictions on custom payment settings while a fixed release is unavailable; a shipped upstream correction is not established.
Advisory / fix evidence · checked 21 Nov 2026
Product: Akaunting. AI system: Fluid Attacks AI SAST Scanner (specific model not disclosed). Team / organization: Fluid Attacks.
CVE identifiers: CVE-2026-118597.
AI and human contribution (source account): The individual first-party advisory explicitly distinguishes detection by AI SAST Scanner from disclosure by Miguel Gómez of Fluid Attacks' Offensive Team. Detailed model architecture and the division of discovery and human validation tasks are not disclosed.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Public individual advisory and matching primary CNA record. Unknown zero-day status is not inferred. The checked page provides an advisory release date but does not independently establish when its present AI-attribution wording was first public.
Remediation status: not established.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 11 Nov 2026. AI attribution date not established by the source. Sources checked 21 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: Not available.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.