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

CVE-2026-6744

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability was found in Bagisto up to 2.3.15. Affected is the function copy of the component Downloadable Link Handler. The manipulation results in server-side request forgery. The attack may be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure and explains: "We already replied on the github advisories. All the security issues are addressed through security advisory. We will fix this in our upcomming releases."

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 · moderate confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the Downloadable Link Handler component of Bagisto e-commerce platform, specifically in the 'copy' function. The vulnerability allows remote attackers to manipulate the function to cause the server to make requests to attacker-controlled URLs, potentially enabling internal service enumeration or data exfiltration.

MitigationUntil an official patch is released, implement input validation on the copy function to restrict URLs to expected domains, and consider deploying a Web Application Firewall to block SSRF attack patterns. Network segmentation can also limit the impact of SSRF against internal services.

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
Low
Availability
Low

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

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 Bagisto installation and version
    Check your web application's version by inspecting composer.json in the bagisto root directory, or access /api/routes or check the admin panel footer for version information. Compare the installed version against the affected range provided by Bagisto security advisories for CVE-2026-6744.
    Affected if The installed version falls within the vulnerable version range for this CVE and no vendor patch has been applied.
  2. Verify Downloadable Link Handler is accessible
    Locate the Downloadable Link Handler controller in your Bagisto installation, typically under packages/Webkul/Admin/src/Controllers/Sales/DownloadableLinkController.php or similar path within the Admin package. Confirm the file exists and the route is registered.
    Affected if The Downloadable Link Handler component is present and its routes are registered in the application.
  3. Confirm copy function endpoint exists
    Search the codebase for a 'copy' function within the Downloadable Link Handler controller class. Check routes/web.php or routes/api.php for any route mapped to this copy action, typically accessible via POST request to a link duplication endpoint.
    Affected if The copy function exists and is mapped to an accessible route without requiring authentication or withinsufficient access controls.
  4. Test if URL parameters are passed to server-side requests
    Review the copy function code to identify if user-supplied URL parameters (such as link_url, url, or file_path) are used directly in HTTP client calls without validation. Look for usage of file_get_contents, curl, or Laravel HTTP client methods with unsanitized input.
    Affected if The copy function accepts URL parameters and uses them in server-side HTTP requests without proper validation or allowlist filtering.
  5. Check for existing input validation
    Inspect the copy function for validation logic that restricts URLs to expected domains or validates URL schemes. Look for validation rules in the controller or request class that whitelist permitted domains or block external URLs.
    Affected if No input validation exists, or the validation can be bypassed, allowing arbitrary URLs to be passed to server-side requests.

You are affected if you are running a vulnerable version of Bagisto with the Downloadable Link Handler enabled and the copy function accepts unsanitized URL input that the server will process.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until an official patch is released, implement input validation on the copy function to restrict URLs to expected domains, and consider deploying a Web Application Firewall to block SSRF attack patterns. Network segmentation can also limit the impact of SSRF against internal services.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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