FreeScout: Incomplete fix for CVE-2026-40570: load_customer_info exposes cross-visibility customer PII
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 1.8.231
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.8.231.
- 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? →
- 25/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
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
FreeScout, a self-hosted help desk and shared mailbox application, has an incomplete fix for a flaw that lets a logged-in agent without admin rights view customer records they should not be able to see when the limit-customer-visibility setting is on. An attacker can do this remotely, and the exposed data can include names, email addresses, phone numbers, postal addresses, and confidential internal agent notes.
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.231, when limit_user_customer_visibility is enabled, the load_customer_info AJAX action performs a global lookup using an attacker-controlled customer email and checks only whether the agent can access a separately supplied mailbox. A non-admin agent can name an accessible mailbox and retrieve an unrelated customer's rendered profile without invoking CustomerPolicy::view(). The response can expose names, email addresses, phone numbers, company and job information, postal addresses, social profiles, websites, and confidential internal agent notes. This issue is fixed in version 1.8.231.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- 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 44 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.8.231.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- freescout-help-desk freescout
fixed in 1.8.231
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-103984
Is CVE-2026-103984 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-103984?
freescout: before 1.8.231.Source: cve.now feed data
How do I fix CVE-2026-103984?
Upgrade to a fixed version: 1.8.231.Source: cve.now feed data