# CVE-2026-21451: Bagisto has HTML Filter Bypass that Enables Stored XSS

> Attackers can bypass HTML filters in the CMS editor to inject malicious scripts, leading to administrator account takeover and backend hijacking.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jan 2026
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-2mwc-h2mg-v6p8

## What is CVE-2026-21451?

CVE-2026-21451 is a medium-severity cross-site scripting vulnerability in bagisto, published on 2 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Bagisto is an open source laravel eCommerce platform. A stored Cross-Site Scripting (XSS) vulnerability exists in Bagisto prior to version 2.3.10 within the CMS page editor. Although the platform normally attempts to sanitize `<script>` tags, the filtering can be bypassed by manipulating the raw HTTP POST request before submission. As a result, arbitrary JavaScript can be stored in the CMS content and executed whenever the page is viewed or edited. This exposes administrators to a high-severity risk, including complete account takeover, backend hijacking, and malicious script execution. Version 2.3.10 fixes the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including bagisto/bagisto. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bagisto/bagisto` | Packagist | All versions | 2.3.10 |
| `bagisto/bagisto` | Packagist | All versions | 2.3.10 |

Products: Webkul Bagisto.

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

Upgrade bagisto/bagisto to 2.3.10 or later.

## Is CVE-2026-21451 being exploited?

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

## Other vulnerabilities in bagisto

- [CVE-2026-21448](https://insights.sbomify.com/CVE-2026-21448/): Bagisto has Normal & Blind SSTI from low-privilege user when ordering product (high 8.9)
- [CVE-2026-21446](https://insights.sbomify.com/CVE-2026-21446/): Bagisto Missing Authentication on Installer API Endpoints (high 8.8)
- [CVE-2023-36237](https://insights.sbomify.com/CVE-2023-36237/): Bagisto Cross-Site Request Forgery vulnerability (high 8.8)
- [CVE-2023-33570](https://insights.sbomify.com/CVE-2023-33570/): Code injection in n/a (high 8.8)
- [CVE-2019-16403](https://insights.sbomify.com/CVE-2019-16403/): Authorization Bypass Through User-Controlled Key in Bagisto (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21451 is a medium-severity cross-site scripting vulnerability in bagisto, published on 2 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21451 exists.

Affected packages and fixed versions:
- bagisto/bagisto (Packagist): affected all versions; fixed in 2.3.10
- bagisto/bagisto (Packagist): affected all versions; fixed in 2.3.10

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-21451/ (Markdown: https://insights.sbomify.com/CVE-2026-21451/index.md)
```

## Sources

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

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