Quick answers
- Is CVE-2026-48811 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48811 being exploited in the wild.
- How severe is CVE-2026-48811?
- Medium severity, with a CVSS score of 4.3, published 29 May 2026.
- Which products and versions are affected?
- FreeScout Help Desk FreeScout < 1.8.221.
- Is there a fix for CVE-2026-48811?
- A patch was published on 2026-05-29: Fix released in version 1.8.221 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48811 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48811?
- Check whether you run FreeScout Help Desk FreeScout at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization check in the ThreadPolicy::delete policy allows users to delete internal notes (threads of type NOTE) based solely on authorship. The vulnerable component fails to verify if the requesting user still maintains active membership or access rights to the mailbox containing the conversation. An attacker with low-privileged credentials can exploit this by sending a crafted POST request to the AJAX conversation endpoint with a specific thread ID. This results in permanent deletion of the note from the database, bypassing intended access revocations. The issue is resolved in version 1.8.221 by adding a mailbox membership verification step to the deletion logic.
Affected products
- FreeScout FreeScout < 1.8.221
Timeline
- 2026-05-28: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: CVE published to NVD
- 2026-05-29: patched: Fix released in version 1.8.221