CVE-2026-6744: Bagisto · Server-Side Request Forgery
Affects BagistoSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bagisto | Affected
| Fixed in– |
Packagistbagisto/bagistopkg:composer/bagisto/bagistoOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor has stated that the issue will be fixed in upcoming releases but has not yet released an official patch or temporary fix. Users should monitor the vendor's advisories and update to the fixed version once it is available. Until then, consider restricting network access from the Bagisto server to sensitive internal resources as a temporary measure.
Description
CVE-2026-6744 is a server-side request forgery (SSRF) vulnerability in Bagisto versions up to 2.3.15. It affects the copy function of the Downloadable Link Handler component. The vulnerability can be exploited remotely without user interaction and has a medium severity rating with a CVSS 4.0 score of 5.3. The vendor has acknowledged the issue and plans to address it in upcoming releases but has not yet provided an official patch. Exploit details have been made public, but no known exploits are reported in the wild at this time.