CVE-2026-40497: freescout · Cross-site Scripting
Affects freescoutSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 1.8.213 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.213
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade freescout and freescout-help-desk/freescout to 1.8.213.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| freescout-help-deskfreescout | Affected
| Fixed in
|
GitHubfreescout-help-desk/freescoutpkg:github/freescout-help-desk/freescoutOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade FreeScout to version 1.8.213 or later, which contains the updated fix that properly addresses the incomplete sanitization of the mailbox signature field. Until upgraded, restrict mailbox settings access to trusted users only, as exploitation requires such permissions. Patch status is not explicitly stated in the advisory fields, but the description confirms version 1.8.213 contains the fix.
Description
FreeScout versions prior to 1.8.213 contain a cross-site scripting (XSS) vulnerability due to improper sanitization of the mailbox signature field. The vulnerability arises because the sanitization function removes certain dangerous tags but does not remove <style> tags, allowing CSS injection. An attacker with mailbox settings access can inject CSS that exfiltrates CSRF tokens from other agents or admins viewing the mailbox, enabling privilege escalation. This issue is a partial regression of a previous fix and is addressed in version 1.8.213.