FreeScout CVE-2026-41192

Exploitation requires authenticated access to a FreeScout mailbox (PR:L) with permissions to view at least one shared conversation containing attachments uploaded by other users. The attacker must have sufficient technical capability to intercept or inspect API responses (via browser tools or proxy) to extract encrypted attachment IDs from load_attachments calls. The vulnerable draft-saving endpoint must be accessible over the network (AV:N), which is standard for all FreeScout installations. No special server configuration, non-default features, or elevated privileges beyond basic mailbox user access are required. User interaction from victims is not needed (UI:N). The vulnerability cannot be exploited by unauthenticated attackers or users without mailbox access. Exploitation is limited to deleting attachments in conversations the attacker can already view - they cannot blindly delete arbitrary files or access content outside their existing conversation visibility scope.

Real-world risk is MODERATE despite the 7.1 CVSS score. The CVSS vector (AV:N/AC:L/PR:L/UI:N) indicates network-accessible exploitation requiring only low-privilege authentication with no user interaction, correctly reflecting the attack mechanics. The High Integrity impact (I:H) captures the ability to delete attachments, while Low Availability impact (A:L) reflects service disruption from lost data. However, practical exploitation requires: (1) valid mailbox credentials (PR:L), (2) access to shared conversations containing target attachments, and (3) knowledge of the draft-saving API mechanics. No EPSS score is available, and CISA KEV status is negative, suggesting no widespread exploitation observed. No public POC is explicitly referenced beyond the fix commit, though the GitHub security advisory (GHSA-cv36-2j23-x6g3) provides sufficient technical detail for proof-of-concept development. This is a real access control flaw with confirmed vendor patch, but exploitation requires insider or compromised-credential scenarios rather than anonymous internet attacks. Priority should be HIGH for organizations using FreeScout with multiple mailbox users sharing conversations, MEDIUM for single-user deployments where credential compromise is the only path.

An authenticated support agent with access to a shared customer mailbox uses their browser developer tools to inspect the load_attachments API response for a conversation containing sensitive documents uploaded by colleagues. They extract encrypted attachment IDs from the JSON response, then craft a save_draft request for one of their own draft replies, populating the attachments_all[] parameter with the stolen encrypted IDs while omitting them from the retained attachment list. The server decrypts the IDs, fails to verify the agent's ownership of those attachments, and calls Attachment::deleteByIds(), permanently removing the files from storage and database. The original conversation now displays missing attachment placeholders, disrupting customer support operations and potentially causing data loss.