dbcve.org
CWE-613Weakness · CWE-613

CVE-2026-41902

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Prior to version 1.8.217, the /user-setup/{hash} endpoint accepts a 60-character random invite_hash to set a new user's password. The endpoint performs no expiration check — the hash remains valid indefinitely until consumed. Combined with realistic hash-leakage scenarios (forwarded invite emails, HTTP referrer to external CDNs on the setup page, server-side log exposure, abandoned invite emails in shared inboxes), this enables unauthenticated permanent account takeover months or years after invite issuance. If the leaked invite was sent to an admin, the takeover yields admin access. This issue has been patched in version 1.8.217.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FreeScout's /user-setup/{hash} endpoint accepts a 60-character invite hash without any expiration validation, allowing the hash to remain valid indefinitely until used. Combined with realistic leakage scenarios (email forwarding, HTTP referrer leaks, server logs, or abandoned emails), this enables unauthenticated attackers to take over user accounts months or years after invite issuance, including admin accounts.

MitigationUpgrade to version 1.8.217 or later to patch this vulnerability. Additionally, revoke and re-issue all outstanding user invites that may have been exposed through leakage vectors.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FreeScout installation and version
    Locate the FreeScout installation directory and check the version file (commonly found in composer.json or a VERSION file in the application root). Alternatively, access the admin panel and navigate to the System Info or About section to view the installed version.
    Affected if The installed version is below 1.8.217 (e.g., 1.8.200, 1.7.x, or earlier releases).
  2. Identify outstanding user invites
    Access the FreeScout admin panel and navigate to the Users, Members, or Invite management section. Look for any pending or unused user invitation records that were created and may remain valid.
    Affected if There are any pending user invites present in the system, especially those created months ago that have not been used or revoked.
  3. Review invite expiration configuration
    Examine the FreeScout configuration files (typically in config/ directory or .env file) for any settings related to invite token expiration, invite validity period, or hash timeout. Also check the application code for any expiration validation logic in the user-setup controller.
    Affected if No expiration time or validity period is configured for invite hashes, or the code lacks expiration validation checks for the /user-setup/{hash} endpoint.
  4. Audit server and email logs for invite hash exposure
    Review web server access logs, application logs, and email server logs for any instances of the 60-character invite hash pattern appearing in URLs, referrer headers, or email metadata. Check if any invite hashes may have been logged or forwarded.
    Affected if Any invite hashes are found in logs, forwarding chains, or other leakage vectors indicating potential exposure.

A user is affected if their FreeScout installation is version 1.8.216 or earlier AND there are outstanding user invites that could have been exposed through leakage vectors, since the endpoint lacks expiration validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.8.217 or later to patch this vulnerability. Additionally, revoke and re-issue all outstanding user invites that may have been exposed through leakage vectors.

Recommended fix High confidence

1.8.217

  1. Backup the current FreeScout installation and database before upgrading
  2. Check the current installed version of FreeScout
  3. Upgrade FreeScout to version 1.8.217 following the official upgrade instructions (typically via composer update or the provided upgrade script)
  4. Verify the installation was successful and the version shows 1.8.217 or higher
  5. Confirm the /user-setup/{hash} endpoint now properly validates hash expiration
Caveat Review release notes for 1.8.217; minor version upgrades in Laravel apps may include configuration or database changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41902 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data