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

Published May 29, 2026
·
Updated

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 PERMEDITCONVERSATIONS 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.

Affected Software

1 affected component
Freescout freescout<1.8.221

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade FreeScout to a version that resolves this vulnerability.

    Fixed in 1.8.221

Event History

May 29, 2026
CVE Published
via MITRE·07:48 PM
Data Sourced
via MITRE·07:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-48810?

CVE-2026-48810 has a medium severity rating of 4.3.

2

How do I fix CVE-2026-48810?

To fix CVE-2026-48810, update FreeScout to version 1.8.221 or later.

3

What type of vulnerability is CVE-2026-48810?

CVE-2026-48810 is an authorization bypass vulnerability due to a missing mailbox membership check.

4

Who is affected by CVE-2026-48810?

Users of FreeScout prior to version 1.8.221 are at risk from CVE-2026-48810.

5

What can be exploited in CVE-2026-48810?

CVE-2026-48810 can be exploited to allow unauthorized users to edit threads by bypassing the authorization checks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203