{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11942 exists.","fix":"No fix has been published for CVE-2026-11942 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11942 is a medium-severity cross-site scripting vulnerability in Akaunting, published on 22 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-11942 and fix it if it is affected.\n\nWhat it is: CVE-2026-11942 is a medium-severity cross-site scripting vulnerability in Akaunting, published on 22 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11942 exists.\n\nAffected product: Akaunting. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-11942/ (Markdown: https://insights.sbomify.com/CVE-2026-11942/index.md)","id":"CVE-2026-11942","markdown":"https://insights.sbomify.com/CVE-2026-11942/index.md","name":"CVE-2026-11942","record":{"aliases":["GHSA-rqfr-jhc5-r4q9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Akaunting accounting software","requires_auth":"high_privilege","summary":"Authenticated users can inject malicious scripts into record names, leading to stored XSS attacks against other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Fluid Attacks","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Akaunting 3.1.21 contains an authenticated stored cross-site scripting vulnerability in the reusable delete confirmation flow. A user with permission to create or modify records, such as Items, can store HTML/JavaScript in the record name.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Akaunting 3.1.21 - Stored XSS in delete confirmation modal","id":"CVE-2026-11942","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Akaunting 3.1.21 - Authenticated stored XSS in document timeline","id":"CVE-2026-11943"},"packages":[],"prev":{"headline":"Use-after-free in connection ID iterator and FFI functions","id":"CVE-2026-11941"},"products":["Akaunting"],"published":"2026-06-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["Akaunting"]},"summary":"Authenticated users can inject malicious scripts into record names, leading to stored XSS attacks against other users.","url":"https://insights.sbomify.com/CVE-2026-11942/"}