# CVE-2026-35584: Missing authorization in freescout

> Unauthenticated attackers can manipulate thread read status and enumerate valid thread IDs in FreeScout due to missing authorization checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-873c-r7v5-g98v

## What is CVE-2026-35584?

CVE-2026-35584 is a medium-severity missing authorization vulnerability in freescout-help-desk freescout, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Prior to 1.8.212, the endpoint GET /thread/read/{conversation_id}/{thread_id} does not require authentication and does not validate whether the given thread_id belongs to the given conversation_id. This allows any unauthenticated attacker to mark any thread as read by passing arbitrary IDs, enumerate valid thread IDs via HTTP response codes (200 vs 404), and manipulate opened_at timestamps across conversations (IDOR). This vulnerability is fixed in 1.8.212.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-35584?

It affects 1 product.


Products: Freescout Freescout.

## How do I fix CVE-2026-35584?

No fix has been published for CVE-2026-35584 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35584 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35584 exists.

Public exploit code:

- POC - CVE-2026-35584 (github_poc): https://github.com/Spoo1k/CVE-2026-35584

## Other vulnerabilities in freescout-help-desk freescout

- [CVE-2026-28289](https://insights.sbomify.com/CVE-2026-28289/): FreeScout 1.8.206 Patch Bypass for CVE-2026-27636 via Zero-Width Space Character Leads to Remote Code Execution (critical 10.0)
- [CVE-2026-27637](https://insights.sbomify.com/CVE-2026-27637/): FreeScout's Predictable Authentication Token Enables Account Takeover (critical 9.8)
- [CVE-2026-32754](https://insights.sbomify.com/CVE-2026-32754/): FreeScout: Stored XSS via Unescaped Email Template Rendering ({!! $thread->body !!}) (critical 9.3)
- [CVE-2024-29185](https://insights.sbomify.com/CVE-2024-29185/): FreeScout OS Command Injection vulnerability (critical 9.1)
- [CVE-2026-40498](https://insights.sbomify.com/CVE-2026-40498/): FreeScout has Authentication Bypass and Information Disclosure in SystemController via /system/cron (high 8.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35584 and fix it if it is affected.

What it is: CVE-2026-35584 is a medium-severity missing authorization vulnerability in freescout-help-desk freescout, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35584 exists.

Affected product: freescout-help-desk freescout. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35584/ (Markdown: https://insights.sbomify.com/CVE-2026-35584/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35584
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35584
- OSV: https://osv.dev/vulnerability/CVE-2026-35584

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35584/
Summaries are generated and may contain mistakes; the official description above is the record.