dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-41906

HIGH · 7.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 →
77/100
Remediation priority · High
Remotely reachable 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.214, the Change Customer modal correctly hides out-of-scope customers through the mailbox-filtered search endpoint, but the backend conversation_change_customer action accepts any supplied customer_email. A low-privileged agent can forge a request and bind a visible conversation to a hidden customer in another mailbox. This issue has been patched in version 1.8.214.

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 prior to 1.8.214 has an authorization bypass where the backend conversation_change_customer action accepts any supplied customer_email without validating mailbox scope, allowing low-privileged agents to forge requests and bind visible conversations to hidden customers from other mailboxes.

MitigationUpgrade FreeScout to version 1.8.214 or later to patch the vulnerable backend action that lacks proper mailbox-scope validation on customer assignment.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Identify FreeScout version
    Check the version file typically located at /var/www/html/FreeScout/version or view the footer of the admin panel for the installed version number
    Affected if version is prior to 1.8.214 (1.8.213 or lower)
  2. Confirm agent user role exists
    Log into FreeScout as a low-privileged agent user (not admin) and verify they have access to the conversation management interface
    Affected if agent role exists and has conversation access permissions
  3. Test conversation_change_customer endpoint behavior
    Using a low-privileged agent account, attempt to change the customer on a conversation using the backend action - observe if the system accepts a customer_email from a different mailbox without rejecting it
    Affected if the backend accepts any customer_email without validating it belongs to the same mailbox as the conversation
  4. Inspect for missing mailbox scope validation
    Review the backend code for conversation_change_customer action (typically in Modules/Filters or similar handler classes) and check if customer_email parameter is validated against the conversation's mailbox before assignment
    Affected if no mailbox/scope validation code is found before customer assignment in that action

If FreeScout version is below 1.8.214 AND low-privileged agents can access the conversation_change_customer action without mailbox-scope validation, the environment is affected by this authorization bypass.

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 FreeScout to version 1.8.214 or later to patch the vulnerable backend action that lacks proper mailbox-scope validation on customer assignment.

Recommended fix High confidence

FreeScout version 1.8.214 or later

  1. Create a complete backup of the FreeScout installation including database and files before proceeding with the upgrade
  2. Identify your current FreeScout version by checking the installation or admin dashboard
  3. Download FreeScout version 1.8.214 or later from the official GitHub repository (github.com/freescout-helpdesk/freescout)
  4. Follow the standard FreeScout upgrade procedure: upload the new files, then run any pending database migrations
  5. Verify the upgrade was successful by checking the version in the admin panel
  6. Test the Change Customer functionality to confirm the vulnerability is remediated - ensure agents can no longer assign conversations to customers outside their mailbox scope
  7. Review admin audit logs if available to confirm no exploitation occurred prior to the upgrade
Caveat Review the FreeScout release notes between your current version and 1.8.214 for any potential breaking changes or required configuration updates

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41906 — 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-41906 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