Cette page n'a pas encore été traduite dans votre langue. Affichage du contenu en anglais pendant que nous y travaillons.

💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.

CVE-2026-35584: IDOR in Laravel FreeScout Help Desk

Plateforme

php

Composant

laravel

Corrigé dans

1.8.212

Traduction vers votre langue…

CVE-2026-35584 is an Insecure Direct Object Reference (IDOR) vulnerability affecting Laravel FreeScout help desk systems. This flaw allows unauthenticated attackers to manipulate thread read statuses and timestamps across different conversations. The vulnerability impacts versions 1.8.0 through 1.8.211, and a fix is available in version 1.8.212.

Impact et Scénarios d'Attaquetraduction en cours…

An attacker exploiting this IDOR vulnerability can gain unauthorized access to and modify sensitive information within the FreeScout help desk. By crafting malicious requests to the /thread/read/{conversationid}/{threadid} endpoint, they can mark arbitrary threads as read, effectively concealing them from authorized users. Furthermore, they can manipulate the opened_at timestamps associated with conversations, potentially disrupting workflows and creating confusion. This could lead to miscommunication, delayed responses to critical issues, and a compromised view of the overall support ticket status. The ability to enumerate valid thread IDs through HTTP response codes (200 vs 404) further simplifies the exploitation process.

Contexte d'Exploitationtraduction en cours…

CVE-2026-35584 was published on 2026-04-07. Currently, there are no publicly known active campaigns exploiting this vulnerability. No public proof-of-concept (POC) code has been released. The vulnerability is not listed on KEV, and its EPSS score is pending evaluation. Monitor security advisories and threat intelligence feeds for any updates regarding exploitation attempts.

Renseignement sur les Menaces

Statut de l'Exploit

Preuve de ConceptInconnu
CISA KEVNO

EPSS

0.07% (percentile 22%)

CISA SSVC

Exploitationpoc
Automatisableyes
Impact Techniquepartial

Logiciel Affecté

Composantlaravel
Fournisseurfreescout-help-desk
Version minimale1.8.0
Version maximale< 1.8.212
Corrigé dans1.8.212

Classification de Faiblesse (CWE)

Chronologie

  1. Réservé
  2. Publiée
  3. Modifiée
  4. EPSS mis à jour

Mitigation et Contournementstraduction en cours…

The primary mitigation for CVE-2026-35584 is to immediately upgrade to FreeScout version 1.8.212 or later. If upgrading is not immediately feasible, consider implementing temporary workarounds. Implement strict access controls on the /thread/read endpoint, requiring authentication and validating that the provided threadid belongs to the specified conversationid. Web application firewalls (WAFs) can be configured to block requests that attempt to access threads without proper authentication or with mismatched IDs. Regularly review FreeScout configurations to ensure adherence to security best practices. After upgrading, confirm the fix by attempting to access a thread with an invalid thread_id – a 404 error should be returned.

Comment corrigertraduction en cours…

Actualice FreeScout a la versión 1.8.212 o superior para mitigar la vulnerabilidad. Esta actualización implementa la validación necesaria para asegurar que un usuario solo pueda acceder a los hilos de conversación a los que pertenece, previniendo la manipulación y enumeración no autorizada.

Questions fréquentestraduction en cours…

What is CVE-2026-35584 — IDOR in Laravel FreeScout?

CVE-2026-35584 is an Insecure Direct Object Reference (IDOR) vulnerability in Laravel FreeScout help desk systems, allowing unauthorized manipulation of thread statuses and timestamps. It affects versions 1.8.0 through 1.8.211.

Am I affected by CVE-2026-35584 in Laravel FreeScout?

You are affected if you are using Laravel FreeScout versions 1.8.0 through 1.8.211. Upgrade to version 1.8.212 to resolve the vulnerability.

How do I fix CVE-2026-35584 in Laravel FreeScout?

The recommended fix is to upgrade to FreeScout version 1.8.212 or later. As a temporary workaround, implement strict access controls and WAF rules to restrict access to the /thread/read endpoint.

Is CVE-2026-35584 being actively exploited?

Currently, there are no publicly known active campaigns exploiting CVE-2026-35584, and no public proof-of-concept code is available.

Where can I find the official Laravel FreeScout advisory for CVE-2026-35584?

Refer to the official Laravel FreeScout documentation and security advisories for the most up-to-date information regarding CVE-2026-35584 and its remediation.

Ton projet est-il affecté ?

Téléverse ton fichier de dépendances et découvre instantanément si cette CVE et d'autres te touchent.

en directfree scan

Essayez maintenant — sans compte

scanZone.subtitle

Scan manuelSlack/email alertsContinuous monitoringWhite-label reports

Glissez-déposez votre fichier de dépendances

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...