# CVE-2026-45295: FreeScout authorization bypass in open tracking endpoint

Source: https://junglewise.ai/threats/cve-2026-45295-freescout-authorization-bypass-in-open-tracking-endpoint  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-20. Updated: 2026-07-20  
License: CC BY 4.0 with a link back

CVE-2026-45295 · Severity: medium · CVSS 6.5 · Published 2026-07-20

FreeScout is an open-source help desk and shared inbox platform. A security flaw in the email tracking system allows unauthorized individuals to identify valid support conversation IDs and tamper with "read" timestamps. This can lead to the corruption of communication analytics and provide a starting point for further unauthorized access to customer support data.

Vendors: [FreeScout Help Desk](https://junglewise.ai/threats/vendors/freescout-help-desk).

## Quick answers

**Is CVE-2026-45295 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-45295 being exploited in the wild.

**How severe is CVE-2026-45295?** Medium severity, with a CVSS score of 6.5, published 20 July 2026.

**Which products and versions are affected?** FreeScout Help Desk < 1.8.219.

**Is there a fix for CVE-2026-45295?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-45295 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-45295?** Check whether you run FreeScout Help Desk 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.

## Technical details

An authorization bypass exists in the FreeScout open tracking endpoint `GET /thread/read/{conversation_id}/{thread_id}` within `app/Http/Controllers/OpenController.php`. The endpoint, intended to serve a 1x1 tracking pixel, lacks authentication and session checks. Because the server returns a 200 OK for valid ID pairs and a 404 Not Found for invalid ones, an unauthenticated attacker can use a side-channel timing or response oracle to enumerate valid conversation and thread IDs. Furthermore, accessing the endpoint automatically updates the `opened_at` timestamp in the database, allowing attackers to manipulate thread read-status data. The issue is resolved in version 1.8.219.

## Affected products

- freescout-help-desk FreeScout < 1.8.219

## Timeline

- 2026-05-17: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: NVD publication date

## References

- [https://github.com/freescout-help-desk/freescout/security/advisories/GHSA-qjr9-6v9q-3r72](https://github.com/freescout-help-desk/freescout/security/advisories/GHSA-qjr9-6v9q-3r72)