# CVE-2026-21447: Bagisto has IDOR in Customer Order Reorder Functionality

> Authenticated users can access other customers' order details and add items to their cart by manipulating order IDs, exposing sensitive data and enabling fraud.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jan 2026
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-x5rw-qvvp-5cgm

## What is CVE-2026-21447?

CVE-2026-21447 is a high-severity missing authorization vulnerability in bagisto, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bagisto is an open source laravel eCommerce platform. Prior to version 2.3.10, an Insecure Direct Object Reference vulnerability in the customer order reorder function allows any authenticated customer to add items from another customer's order to their own shopping cart by manipulating the order ID parameter. This exposes sensitive purchase information and enables potential fraud. Version 2.3.10 patches the issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

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-21447?

Upgrade bagisto/bagisto to 2.3.10 or later.

## Is CVE-2026-21447 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21447 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-21447 and fix it if it is affected.

What it is: CVE-2026-21447 is a high-severity missing authorization vulnerability in bagisto, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21447 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-21447/ (Markdown: https://insights.sbomify.com/CVE-2026-21447/index.md)
```

## Sources

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

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