# CVE-2026-21446: Bagisto Missing Authentication on Installer API Endpoints

> Unauthenticated attackers can access installer API endpoints to create admin accounts and modify configurations in Bagisto.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-6h7w-v2xr-mqvw

## What is CVE-2026-21446?

CVE-2026-21446 is a high-severity missing authorization vulnerability in bagisto, published on 2 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bagisto is an open source laravel eCommerce platform. In versions on the 2.3 branch prior to 2.3.10, API routes remain active even after initial installation is complete. The underlying API endpoints (`/install/api/*`) are directly accessible and exploitable without any authentication. An attacker can bypass the Ib installer entirely by calling the API endpoints directly. This allows any unauthenticated attacker to create admin accounts, modify application configurations, and potentially overwrite existing data. Version 2.3.10 fixes the issue.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bagisto/bagisto` | Packagist | From 2.3.0 | 2.3.10 |
| `bagisto/bagisto` | Packagist | From 2.3.0 | 2.3.10 |

Products: Webkul Bagisto.

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

Upgrade bagisto/bagisto to 2.3.10 or later.

## Is CVE-2026-21446 being exploited?

There is no known exploitation of CVE-2026-21446 in the wild and no public exploit code.

## 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-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)
- [CVE-2019-14933](https://insights.sbomify.com/CVE-2019-14933/): Bagisto CSRF Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21446 is a high-severity missing authorization vulnerability in bagisto, published on 2 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-21446 in the wild and no public exploit code.

Affected packages and fixed versions:
- bagisto/bagisto (Packagist): affected from 2.3.0; fixed in 2.3.10
- bagisto/bagisto (Packagist): affected from 2.3.0; 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-21446/ (Markdown: https://insights.sbomify.com/CVE-2026-21446/index.md)
```

## Sources

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

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