# CVE-2026-6745: Bagisto Custom Scripts cross site scripting

> Attackers can inject malicious scripts via the Custom Scripts Handler in Bagisto, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-65fp-7g2v-658r

## What is CVE-2026-6745?

CVE-2026-6745 is a medium-severity cross-site scripting vulnerability in Bagisto, published on 21 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was determined in Bagisto up to 2.3.15. Affected by this vulnerability is an unknown functionality of the component Custom Scripts Handler. This manipulation causes cross site scripting. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. 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."

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-6745?

2 open source packages ship an affected version, including bagisto/bagisto.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bagisto/bagisto` | Packagist | All versions to 2.3.15 | None |
| `bagisto/bagisto` | Packagist | All versions to 2.3.15 | None |

## How do I fix CVE-2026-6745?

No fix has been published for CVE-2026-6745 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6745 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6745 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6745 and fix it if it is affected.

What it is: CVE-2026-6745 is a medium-severity cross-site scripting vulnerability in Bagisto, published on 21 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6745 exists.

Affected packages and fixed versions:
- bagisto/bagisto (Packagist): affected all versions up to 2.3.15; no fix listed
- bagisto/bagisto (Packagist): affected all versions up to 2.3.15; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6745/ (Markdown: https://insights.sbomify.com/CVE-2026-6745/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6745
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6745
- OSV: https://osv.dev/vulnerability/CVE-2026-6745

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6745/
Summaries are generated and may contain mistakes; the official description above is the record.