# CVE-2026-32752: FreeScout: Broken Access Control in ThreadPolicy — Any User Can Read/Edit All Customer Messages

> Any authenticated user can read and modify all customer messages across all mailboxes, bypassing permission controls in FreeScout.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-wxg5-g9vv-v8g9

## What is CVE-2026-32752?

CVE-2026-32752 is a missing authorization vulnerability in freescout-help-desk freescout, published on 19 Mar 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. In versions 1.8.208 and below, the ThreadPolicy::edit() method contains a broken access control vulnerability that allows any authenticated user (regardless of role or mailbox access) to read and modify all customer-created thread messages across all mailboxes. This flaw enables silent modification of customer messages (evidence tampering), bypasses the entire mailbox permission model, and constitutes a GDPR/compliance violation. The issue has been fixed in version 1.8.209.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Freescout Freescout.

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

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

## Is CVE-2026-32752 being exploited?

There is no known exploitation of CVE-2026-32752 in the wild and no public exploit code.

## 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-32752 and fix it if it is affected.

What it is: CVE-2026-32752 is a missing authorization vulnerability in freescout-help-desk freescout, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32752 in the wild and no public exploit code.

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-32752/ (Markdown: https://insights.sbomify.com/CVE-2026-32752/index.md)
```

## Sources

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

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