DEV Community

andreagomez
andreagomez

Posted on

FreeScout Personal API Keys Still Depend on Mailbox Permissions

FreeScout Personal API Keys Still Depend on Mailbox Permissions

FreeScout is a self-hosted shared-mailbox helpdesk. A ZoomEye count-only query on November 18, 2026 found 1,746 matches for title="FreeScout" and 1,260 for app="FreeScout". The difference suggests that some deployments can be identified by both fields and others only by title, but the counts still describe indexed services rather than confirmed customer environments.

The query used page 1, page size 1 and sub_type=all. Only totals were collected. A result could be a demo, an internal helpdesk or a reverse-proxy page with the product title. It could also miss a customized instance. Treat the count as a starting inventory and keep the exact query and timestamp with any later comparison.

FreeScout's API and Webhooks module supports personal API keys. The API documentation says a newly created user does not have access to any mailboxes by default. That default is a useful separation between account existence and helpdesk data. The effective authority of a personal key depends on the user's permissions, mailbox assignments and enabled modules.

Review API keys as user credentials rather than application-wide secrets. Each key should have an owner, purpose, creation time and revocation record. If the application enables personal keys, restrict who can manage users and review the setting that permits that capability. Remove keys for departed staff or unused integrations. A shared administrator key makes it harder to attribute ticket changes.

Test mailbox boundaries with two agents. Give each account access to one mailbox and confirm that the API cannot read conversations, attachments or customer records in the other mailbox. Test list, search, export and delete operations separately. A response that hides one mailbox from a list does not prove that a direct object identifier is denied.

Review the user portal and public endpoints. Customer-facing forms can create conversations, upload attachments and send email. They should not expose internal notes, other customers or administrative fields. Check rate limits, spam controls and the modules that allow email fetching. The helpdesk server often connects to IMAP and SMTP accounts with broad mailbox authority, so a compromise can lead to mail delivery changes rather than only data disclosure.

Patch FreeScout and its modules as one inventory. The core application, API module and third-party plugins can have different release cycles. Record the versions and verify that the public site is not behind an unintended basic authentication prompt that breaks webhooks or integrations. If the site uses HTTPS, check redirects and proxy headers so generated links and API callbacks use the correct external URL.

Monitor mailbox permission changes, new users, API-key creation and bulk conversation exports. Correlate those events with login source addresses and mail-fetch jobs. When an agent leaves, disable the account, revoke personal keys, remove mailbox access and inspect whether the account created forwarding or notification rules. A disabled login alone does not remove an API key that was already issued.

The search result gives a useful population for ownership review. The product title and app count should be retained together, because either can produce a different inventory after an upgrade. The security decision comes from mailbox assignments, user lifecycle and key revocation, not from the number of indexed pages.

References

Top comments (0)