Vulnerability in Laravel FreeScout (CVE-2026-45294)
Summary
Vulnerability in Laravel FreeScout (CVE-2026-45294). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.8.219 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.219, the password reset endpoint returns visually distinct responses depending on whether the submitted email address belongs to an existing user account, allowing unauthenticated attackers to enumerate valid helpdesk agent email addresses. This vulnerability is fixed in 1.8.219.
Source: NIST National Vulnerability Database NVD
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-45294 has been found in Laravel FreeScout.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade Laravel FreeScout to 1.8.219 or later.
If unsure, ask your IT team or search "Laravel FreeScout CVE-2026-45294" on the vendor's site.
CVE-2026-45294 (Laravel FreeScout) — CWE-203 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.8.219 — 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-203) exists in Laravel FreeScout.
Check the vendor advisory for the affected versions of Laravel FreeScout.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.8.219.
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.219ステージング環境で 1.8.219 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com