LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Bagisto stores before version 2.3.10 allow a logged-in customer to access reorder data tied to another customer's order. This can reveal purchase information and may let someone place items from another customer's order into their own cart, creating privacy and fraud risk for eCommerce operators.

Executive priority

Treat as a high-priority eCommerce privacy issue. It can expose customer purchase details and create fraud concerns, but current sources do not show public exploitation. Patch affected Bagisto stores promptly, especially customer-facing production sites.

Technical view

CVE-2026-21447 is an IDOR in Bagisto customer order reorder functionality. The advisory states authenticated customers could manipulate an order ID parameter to add items from another customer's order to their cart. It is rated CVSS 7.1 high, with network access, low complexity, low privileges, no user interaction, high confidentiality impact, and low integrity impact.

Likely exposure

Internet-facing Bagisto storefronts running versions earlier than 2.3.10 are the likely exposure. Exploitation requires a valid customer account, so anonymous users are not described as affected in the provided sources.

Exploitation context

No active exploitation is stated in the supplied sources, and the CVE is not marked KEV. The vulnerability is still practical because customer login is normally available on eCommerce sites and the issue is described as low complexity.

Researcher notes

The root issue maps to broken authorization, including CWE-284 and CWE-639. Validation should focus on confirming object-level authorization checks around customer reorder requests, without attempting cross-customer access in production unless explicitly authorized.

Mitigation direction

  • Upgrade Bagisto to version 2.3.10 or later.
  • Review the GitHub advisory and vendor commit for deployment-specific guidance.
  • If immediate upgrade is delayed, assess whether reorder functionality can be temporarily restricted.
  • Monitor customer order and cart activity for suspicious cross-account patterns.

Validation and detection

  • Inventory Bagisto deployments and confirm installed versions.
  • Prioritize any instance running a version earlier than 2.3.10.
  • Confirm the patch corresponding to the referenced commit is present.
  • Review access logs for unusual authenticated reorder activity after disclosure.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21447 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-21447Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
bagistobagisto< 2.3.10Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.