Quick answers
- Is CVE-2026-62856 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62856 being exploited in the wild.
- How severe is CVE-2026-62856?
- High severity, with a CVSS score of 7.7, published 6 November 2026.
- Which products and versions are affected?
- FreeScout prior to 1.8.226.
- Is there a fix for CVE-2026-62856?
- Yes: fixed in 1.8.226. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62856 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-62856?
- Check whether you run FreeScout at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.8.226
Technical details
The polycast/receive endpoint fails to escape SQL LIKE wildcards in channel names, and channel authorization checks only validate names with specific prefixes. An unauthenticated attacker with a valid CSRF token can supply wildcard characters in the channel name parameter to bypass authorization checks and retrieve notifications intended for other users. The vulnerability combines SQL injection in the LIKE query with missing access control on notification payload generation, allowing cross-user data exposure.
Affected products
- FreeScout FreeScout prior to 1.8.226
Timeline
- 2026-11-06: disclosed