FreeScout: Missing Authorization and Exposure of Sensitive Information to an Unauthorized Actor and Authorization Bypass Through…
- Exploited
- No known exploitation
- Fix
- Fixed in 1.8.226
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.8.226.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
FreeScout, a self-hosted help desk and shared mailbox tool, has a flaw that lets a logged-in user with restricted access read conversations they should not see, including replies, internal notes, recipient addresses, and attachment download links. The attack can be carried out remotely over the network, but it requires the attacker to have a valid low-privilege account.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
FreeScout is a self-hosted help desk and shared mailbox. Prior to 1.8.226, RealtimeConvNewThread checks only general mailbox access and does not apply the conversation-level restriction for users configured to see only assigned conversations. A restricted authenticated user can subscribe to predictable conv.<conversation_id> Polycast channels for other conversations in the same mailbox. New event payloads can expose complete replies, internal notes, recipient addresses, conversation state, assignee data, attachment names, and attachment URLs containing valid download tokens. This issue is fixed in version 1.8.226.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.8.226.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- freescout-help-desk freescout
fixed in 1.8.226
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62852
Is CVE-2026-62852 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-62852?
freescout: before 1.8.226.Source: cve.now feed data
How do I fix CVE-2026-62852?
Upgrade to a fixed version: 1.8.226.Source: cve.now feed data