# CVE-2026-48810: FreeScout: Thread Edit Authorization Bypass via Missing Mailbox Check

> An attacker with edit permissions can modify threads in mailboxes they no longer have access to due to missing membership checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-3w38-h42v-3h6w

## What is CVE-2026-48810?

CVE-2026-48810 is a medium-severity missing authorization vulnerability in freescout-help-desk freescout, published on 29 May 2026. Any signed-in user can exploit it over the network, 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.221, while investigating the ThreadPolicy::delete issue reported previously, the same missing mailbox membership check was found in the sibling ThreadPolicy::edit method. A user with the PERM_EDIT_CONVERSATIONS permission who created a message or internal note in Mailbox A can rewrite that thread's body after an administrator removes them from Mailbox A, because the policy checks only authorship and a global permission flag — not current mailbox membership. This vulnerability is fixed in 1.8.221.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-48810 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48810 is a medium-severity missing authorization vulnerability in freescout-help-desk freescout, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48810 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-48810/ (Markdown: https://insights.sbomify.com/CVE-2026-48810/index.md)
```

## Sources

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

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