dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-41905

HIGH · 7.7 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 →
83/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.217, Helper::sanitizeRemoteUrl() in app/Misc/Helper.php follows HTTP redirects via curlGetLastRedirectedUrl() but then re-validates the original URL instead of the final redirect destination. An attacker who can supply any URL that passes the initial host check can redirect FreeScout to internal HTTP services (cloud metadata, internal APIs, RFC1918 ranges) that would normally be blocked. 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 Helper::sanitizeRemoteUrl() function follows HTTP redirects but validates the original URL instead of the final redirect destination. This allows attackers to bypass host blocklists and access internal services (cloud metadata, RFC1918 addresses, internal APIs) by supplying an initially-valid URL that redirects to protected internal resources.

MitigationUpgrade FreeScout to version 1.8.217 or later to apply the patch that validates the final redirect destination.

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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
    Locate the FreeScout installation directory. Look for standard PHP application files such as index.php, artisan, or composer.json in common web directories (/var/www, /home, /opt, or your web root).
    Affected if FreeScout is present on the system
  2. Identify installed FreeScout version
    Check the version file or composer.json in the FreeScout root directory. Typical location: [installation-path]/VERSION.txt or [installation-path]/composer.json. The version number is also often displayed in the application footer of the web interface.
    Affected if The installed version is lower than 1.8.217
  3. Locate Helper::sanitizeRemoteUrl function
    Search for the file containing the sanitizeRemoteUrl function. In the FreeScout source, this is typically in a Helper.php file under app/Helpers/ or similar. Verify the function code validates the original URL rather than the final redirect destination.
    Affected if The function validates only the initial URL and follows redirects without re-validating the final destination
  4. Check if remote URL fetching is enabled
    Identify if the application uses functionality that calls sanitizeRemoteUrl. This function is typically used when fetching attachments from external URLs, parsing incoming emails with remote content, or integrating with external APIs. Review application logs or configuration for outbound HTTP requests.
    Affected if The application makes outbound HTTP requests that utilize sanitizeRemoteUrl to fetch remote resources

You are affected if FreeScout version is below 1.8.217 AND the application uses any feature that triggers the sanitizeRemoteUrl function to fetch remote URLs.

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.217 or later to apply the patch that validates the final redirect destination.

Recommended fix High confidence

FreeScout version 1.8.217 or later

  1. 1. Back up your FreeScout installation and database before upgrading.
  2. 2. Upgrade FreeScout to version 1.8.217 or later (the fixed release).
  3. 3. Verify the upgrade completed successfully.
  4. 4. Confirm that Helper::sanitizeRemoteUrl() now validates the final redirect destination rather than the original URL.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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