CVE-2026-48810: FreeScout: Thread Edit Authorization Bypass via Missing Mailbox Check
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.
Security readout for executives and security teams
Plain-English summary
FreeScout before 1.8.221 could let a former mailbox member keep editing a thread they previously wrote, if they still had the edit-conversations permission. The business risk is unauthorized alteration of help desk thread content, not service outage or confirmed data theft based on the supplied sources.
Executive priority
Treat this as a targeted integrity issue. It is not critical, but it can undermine trust in help desk records. Prioritize patching where FreeScout handles customer, security, legal, or regulated support conversations.
Technical view
The ThreadPolicy::edit authorization logic missed a current mailbox membership check. It relied on authorship plus PERM_EDIT_CONVERSATIONS, allowing post-removal edits to a thread body. Sources rate it CVSS 3.1 4.3, CWE-285, network reachable, low complexity, low privilege, no user interaction, with low integrity impact.
Likely exposure
Exposure applies to FreeScout versions before 1.8.221. Risk is most relevant where agents or shared-inbox users retain PERM_EDIT_CONVERSATIONS after being removed from a mailbox, especially in organizations with frequent mailbox reassignment or staff turnover.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. Abuse requires an authenticated user with the edit-conversations permission who previously created a message or internal note in the affected mailbox.
Researcher notes
Evidence is limited to the advisory and CVE source details. The key authorization gap is missing mailbox membership validation in ThreadPolicy::edit, sibling to a previously investigated delete-policy issue. No exploit details or broader affected products are supported by the bundle.
Mitigation direction
Upgrade FreeScout to version 1.8.221 or later.
Review the GitHub advisory for vendor-specific guidance.
Restrict PERM_EDIT_CONVERSATIONS to users who currently need it.
Review recent mailbox removals for users retaining edit permissions.
If upgrade is delayed, reduce edit privileges until patched.
Validation and detection
Inventory FreeScout deployments and confirm versions are at least 1.8.221.
List users with PERM_EDIT_CONVERSATIONS and verify current mailbox membership.
Review thread edits by users removed from affected mailboxes.
Check change-management records for mailbox removals before patching.
Confirm help desk content integrity for sensitive conversations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-285 · source CWE mapping
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.