Vulnerability in Laravel FreeScout (CVE-2026-45295)
Summary
Vulnerability in Laravel FreeScout (CVE-2026-45295). Risk of unauthorized operations or information disclosure. Exploitable via GET /thread/read/{conversation_id}/{thread_id}.
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 version 1.8.219, the open tracking endpoint GET /thread/read/{conversation_id}/{thread_id} allows unauthenticated attackers to enumerate valid conversation and thread IDs, and modify thread state (opened_at timestamp) without any authentication. Version 1.8.219 patches the issue.
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-45295 has been found in Laravel FreeScout.
Attackers can target a specific entry point like GET /thread/read/{conversation_id}/{thread_id} over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Laravel FreeScout CVE-2026-45295" on the vendor's site.
CVE-2026-45295 (Laravel FreeScout) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /thread/read/{conversation_id}/{thread_id} / opened_at
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-639) exists in Laravel FreeScout. Attackers reach the vulnerable code path via GET /thread/read/{conversation_id}/{thread_id} without authentication.
Check the vendor advisory for the affected versions of Laravel FreeScout. Attack surface: GET /thread/read/{conversation_id}/{thread_id} / opened_at.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /thread/read/{conversation_id}/{thread_id} requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /thread/read/{conversation_id}/{thread_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /thread/read/{conversation_id}/{thread_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /thread/read/{conversation_id}/{thread_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com