FreeScout: Cross-mailbox conversation existence / internal-id disclosure via the search-by-number (`#`) shortcut (missing mailbox…
- 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? →
- 7/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 in its search-by-number shortcut that lets a logged-in agent who belongs to at least one mailbox confirm that a conversation exists in a mailbox they cannot access and learn its internal conversation and folder IDs. The attack can be carried out remotely over the network with low-privilege login and needs no user action, and it does not expose message content, attachments, or customer data.
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, the search-by-number shortcut in ConversationsController::search() resolves a user-controlled ticket number without applying the mailbox filter or view policy used by the normal search path. An authenticated non-admin agent who is a member of at least one mailbox can request /search with a hash-prefixed ticket number and use the 302 Location header to confirm that a conversation exists in a different mailbox the agent cannot access and learn its internal conversation and folder identifiers. The destination conversation remains protected, so this issue does not disclose message content, attachments, or customer data. 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
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 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-62851
Is CVE-2026-62851 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-62851?
freescout: before 1.8.226.Source: cve.now feed data
How do I fix CVE-2026-62851?
Upgrade to a fixed version: 1.8.226.Source: cve.now feed data