CVE-2026-53595 freescout-help-desk CVE debrief

Who should care

Administrators and users of FreeScout, especially those with activated accounts, should assess their exposure and take immediate action to update to version 1.8.224 or later. Affected operator, platform, vulnerability-management, and security-team impact should be reviewed.

Why it matters

CVE-2026-53595 is a critical vulnerability in FreeScout that allows an anonymous attacker to set the email and password of the lowest-id activated FreeScout account and authenticate as that account. The vulnerability exists in the public endpoint `POST /user-setup/{hash}/{invite_sent_at}` and can be exploited without authentication, cookie, or prior session. The exploitation requires verification of the affected versions and accounts.

• An attacker can set the email and password of the lowest-id activated FreeScout account
• An attacker can authenticate as the lowest-id activated FreeScout account
• The vulnerability can be exploited without authentication, cookie, or prior session
• The exploitation requires verification of the affected versions and accounts

Technical summary

The vulnerability exists in the public endpoint `POST /user-setup/{hash}/{invite_sent_at}` (`OpenController@userSetupSave`) which selects the target account solely by its `invite_hash` column, then overwrites that account's email and password and logs in as it. No authentication, cookie, or prior session is required. After a user activates, FreeScout sets `invite_hash` to the empty string. On MySQL and MariaDB, `VARCHAR` equality ignores trailing spaces, so a single URL-encoded space (`%20`) matches the stored empty string and selects the lowest-id activated user.

Defensive priority

High

Recommended defensive actions

• Review and update FreeScout to version 1.8.224 or later
• Restrict access to the `POST /user-setup/{hash}/{invite_sent_at}` endpoint
• Monitor for suspicious activity on the FreeScout instance
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The vulnerability exists in the public endpoint `POST /user-setup/{hash}/{invite_sent_at}` (`OpenController@userSetupSave`) which selects the target account solely by its `invite_hash` column, then overwrites that account's email and password and logs in as it. No authentication, cookie, or prior session is required.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.