Skip to main content
VulnerabilityPublished Updated

CVE-2026-47123: freescout · Authentication Bypass by Spoofing

Affects freescoutSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.8.220 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.220
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade freescout-help-desk/freescout to 1.8.220.

Affected software

ProductAffectedFixed in
GitHubfreescout-help-desk/freescoutpkg:github/freescout-help-desk/freescoutOther threatsAffected
  • <1.8.220
Fixed in
  • 1.8.220

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade FreeScout to version 1.8.220 or later, where this vulnerability is fixed. There is no indication of an official temporary workaround or mitigation other than applying the update. Patch status is not explicitly stated in the vendor advisory but the description confirms the issue is fixed in 1.8.220. Users should verify they are running this version or newer to remediate the vulnerability.

Description

FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Prior to 1.8.220, the email processing pipeline in FreeScout's FetchEmails command has two code paths for identifying agent (user) replies based on In-Reply-To / References headers. The notification reply path (notify-{thread_id}-{user_id}-...) extracts thread_id and user_id directly from the Message-ID without HMAC verification. An external attacker who can spoof the From address of a helpdesk agent can inject messages that FreeScout processes as legitimate agent replies — which are then automatically forwarded to customers via the legitimate SMTP server. This vulnerability is fixed in 1.8.220.

References

Community reviews

Loading reviews…