FreeScout: Conversation Merge Cross-Mailbox Authorization Bypass
- Exploited
- No known exploitation
- Fix
- Fixed in 1.8.227
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.8.227.
- 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? →
- 8/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 agent merge their own conversation into a conversation in a mailbox they are not authorized to access, which can add threads, attachments, and audit records to that target and delete the source conversation. The attack can be launched remotely by any user with low-privilege login, and it does not reveal the target's existing contents.
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.227, the conversation_merge action records a failed authorization check for the target conversation in response['msg'] and then clears that value inside the source-conversation loop. An authenticated agent can merge a conversation they control into a target conversation in a mailbox they cannot access. The operation injects threads, attachments, and audit records into the unauthorized target and deletes the source conversation, but it does not disclose the target's existing contents. This issue is fixed in version 1.8.227.
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
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.8.227.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- freescout-help-desk freescout
fixed in 1.8.227
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-85744
Is CVE-2026-85744 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-85744?
freescout: before 1.8.227.Source: cve.now feed data
How do I fix CVE-2026-85744?
Upgrade to a fixed version: 1.8.227.Source: cve.now feed data