{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40567 exists.","fix":"No fix has been published for CVE-2026-40567 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40567 is a medium-severity cross-site scripting vulnerability in freescout-help-desk freescout, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40567 and fix it if it is affected.\n\nWhat it is: CVE-2026-40567 is a medium-severity cross-site scripting vulnerability in freescout-help-desk freescout, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40567 exists.\n\nAffected product: freescout-help-desk freescout. 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-40567/ (Markdown: https://insights.sbomify.com/CVE-2026-40567/index.md)","id":"CVE-2026-40567","markdown":"https://insights.sbomify.com/CVE-2026-40567/index.md","name":"CVE-2026-40567","record":{"aliases":["GHSA-q8v4-v62h-5528"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"FreeScout help desk","requires_auth":"none","summary":"Unauthenticated attackers can inject HTML into outgoing support emails via crafted sender names, enabling phishing and tracking pixel attacks.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.213, an unauthenticated attacker can inject arbitrary HTML into outgoing emails generated by FreeScout by sending an email with a crafted From display name. The name is stored in the database without sanitization and rendered unescaped into outgoing reply emails via the `{%customer.fullName%}` signature variable. This allows embedding phishing links, tracking pixels, and spoofed content inside legitimate support emails sent from the organization's address. Version 1.8.213 fixes the issue.","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":"FreeScout has HTML Injection in Outgoing Emails via Unsanitized Customer Name in Signature Variables","id":"CVE-2026-40567","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FreeScout Vulnerable to XSS via Mailbox Signature Due to Incomplete HTML Sanitization","id":"CVE-2026-40568"},"packages":[],"prev":{"headline":"FreeScout vulnerable to SSRF via IMAP/SMTP Connection Test Endpoints","id":"CVE-2026-40566"},"products":["freescout"],"published":"2026-04-21","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-21","vendors":["freescout-help-desk"]},"summary":"Unauthenticated attackers can inject HTML into outgoing support emails via crafted sender names, enabling phishing and tracking pixel attacks.","url":"https://insights.sbomify.com/CVE-2026-40567/"}