Vulnerability in Laravel FreeScout (CVE-2026-47123)
Summary
Vulnerability in Laravel FreeScout (CVE-2026-47123). Data can be tampered with by attackers. Mitigation: upgrade to 1.8.220 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47123 has been found in Laravel FreeScout.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade Laravel FreeScout to 1.8.220 or later.
If unsure, ask your IT team or search "Laravel FreeScout CVE-2026-47123" on the vendor's site.
CVE-2026-47123 (Laravel FreeScout) — CWE-290 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.8.220 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-290) exists in Laravel FreeScout.
Check the vendor advisory for the affected versions of Laravel FreeScout.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to 1.8.220.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'FreeScout' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'FreeScout' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
FreeScoutを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Laravel FreeScout to 1.8.220ステージング環境で 1.8.220 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- report vincent.vulcoord.net