LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47123: FreeScout: Agent Impersonation via Missing HMAC Verification on Notification Reply Message-ID Path

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

FreeScout versions before 1.8.220 can mistake a forged email as a real helpdesk agent reply. If an attacker can spoof an agent’s sender address, FreeScout may forward the attacker’s message to customers through the organization’s legitimate mail server, creating trust, fraud, and reputational risk.

Executive priority

Prioritize patching if FreeScout is customer-facing or handles sensitive support communications. The main business risk is trusted-channel abuse: customers may receive fraudulent messages from your legitimate helpdesk infrastructure.

Technical view

The vulnerable FetchEmails flow has a notification-reply path that parses thread_id and user_id from Message-ID-related headers without HMAC verification. This can let spoofed inbound mail be attributed to an agent and handled as an authenticated reply. The issue is fixed in FreeScout 1.8.220.

Likely exposure

Organizations running FreeScout below 1.8.220 with inbound email processing enabled are the relevant exposure group. Risk is higher where attackers can spoof agent From addresses or where mail authentication controls are weak.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The attack requires spoofing an agent sender address and abusing the notification reply identification path; the advisory rates attack complexity high.

Researcher notes

Focus review on FetchEmails notification-reply handling and Message-ID-derived notify identifiers. Evidence supports missing HMAC verification on one reply-identification path. Do not assume broader FreeScout authentication compromise beyond the documented email-processing behavior.

Mitigation direction

  • Upgrade FreeScout to version 1.8.220 or later.
  • Review the GitHub advisory and fixed commit for vendor-confirmed remediation details.
  • Strengthen inbound email authentication controls against agent-address spoofing.
  • Monitor vendor guidance for any follow-up fixes or operational recommendations.
  • Review customer-facing outbound mail for suspicious agent-attributed replies.

Validation and detection

  • Inventory all FreeScout deployments and confirm their running version.
  • Confirm inbound email processing is disabled or patched on versions below 1.8.220.
  • Review helpdesk and SMTP logs for agent replies not sent by the named agent.
  • Check whether mail controls reject spoofed agent From addresses.
  • Validate the fixed version is deployed in production and backup environments.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-290: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-345: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-47123 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N2.24.7GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-47123Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
freescout-help-deskfreescout< 1.8.220Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-290 · source CWE mapping

Authentication Bypass by Spoofing

Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-345 · source CWE mapping

Insufficient Verification of Data Authenticity

Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.