Bagisto has IDOR in Customer Order Reorder Functionality

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-21447: 0.30% estimated exploitation activity in the next 30 days; percentile 23.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details The vulnerability exists in the reorder method within OrderController.php. Unlike other order-related functions like view, cancel, printInvoice that properly validate customer ownership, the reorder function retrieves orders using only the order ID without verifying that the order belongs to the authenticated customer. Code location: packages/Webkul/Shop/src/Http/Controllers/Customer/Account/OrderController.php Exposed Route: packages/Webkul/Shop/src/Routes/customer-routes.php PoC I. Create victim account and place an order. II. Login as attacker. III. Exploit IDOR and navigate like: http://target.xxx/customer/account/orders/reorder/1 IV. Check…

Published by the source

2 Jan 2026, 22:50 UTC

Last modified by the source

2 Jan 2026, 22:50 UTC

Source last checked

26 Oct 2026, 14:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x5rw-qvvp-5cgm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-21447

Advisory: Bagisto has IDOR in Customer Order Reorder Functionality
IDs: CVE-2026-21447, GHSA-x5rw-qvvp-5cgm
Record: https://patchnext.com/advisories/cve-2026-21447 (revision 1, source checked 26 Oct 2026, 14:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: bagisto/bagisto 2.3.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist bagisto/bagisto: affected < 2.3.10; fixed in 2.3.10

## Suggested inspection (read-only)
- Packagist bagisto/bagisto: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on bagisto/bagisto.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x5rw-qvvp-5cgm (GitHub-reviewed advisory GHSA-x5rw-qvvp-5cgm lists affected ranges: Packagist bagisto/bagisto >=0 <2.3.10)

Commands are suggestions: review each one before running it.