Skip to main content

BeikeShop EUVDEUVD-2026-119864

| CVE-2026-124576 MEDIUM
Improper Enforcement of Behavioral Workflow (CWE-841)
2026-11-09 VulDB
6.9
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach guest order lookup endpoint
  2. Exploit
    Manipulate order_number argument
  3. Impact
    Retrieve unauthorized guest order data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Workflow enforcement
Exploitation Conditions

Exploitation targets the Guest Order Lookup path for orders placed as a guest (customer_id is null); the pre-patch OrderRepo::getOrderByNumber returned such orders by order_number without verifying that the requester owns the order via session data or the api/* Bksessionid header. The CVSS vector is AV:N/AC:L/AT:N/PR:N/UI:N, so exploitation is remote and does not require authentication or user interaction. Limiting factors: the target store must actually use guest checkout so guest orders exist, and the attacker must reach valid/guessable order_number values; the related PayPal create/capture abuse surface additionally requires the PayPal plugin to be active (the fix wraps that path in getPayableOrder with a checkActive('paypal') gate). Customer-owned orders are not affected by this specific guest-authorization gap.

Impact

This is a broken-access-control / insecure-direct-object-reference flaw in BeikeShop's Guest Order Lookup (OrderRepo::getOrderByNumber), classified CWE-841. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, low-complexity, unauthenticated reachability, which is consistent with the patch: before the fix, a guest order could be retrieved by its order_number with no ownership/session check, and the commit introduces isGuestOrderAuthorized() to bind a guest order to a session or Bksessionid header. Impact is rated Low across the board (VC:L/VI:L/VA:L), yielding a Medium score of 6.9 - this is an exposure-of-order-data and limited order/payment-workflow abuse issue, not remote code execution. There is NO EPSS score, NO CISA KEV listing, and NO confirmed public exploit in the input, so there is no signal of active or widespread exploitation; the only priority signal is the vendor/VulDB 'this_month' decision label and the availability of a patch. The affected product (an open-source Laravel e-commerce platform) has a modest deployment footprint, further lowering real-world urgency. Net assessment: a legitimate Medium-severity access-control bug worth patching on a normal cycle, not a high-CVSS emergency; the only partial conflict is that the CWE label (behavioral-workflow enforcement) is vaguer than the code, which clearly shows missing guest-order authorization.

Exploit ScenarioDerived

A remote, unauthenticated attacker queries the guest order lookup with manipulated order_number values and, because the pre-patch getOrderByNumber performs no session/ownership binding for guest orders, retrieves order records belonging to other guests. In deployments using the PayPal plugin, the same unauthorized order access could be leveraged to reach payment create/capture handling for another guest's unpaid order. No public exploit code is identified in the provided sources.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 09, 2026

Guest order records in BeikeShop through 2.0.0.31 can be looked up by order number without proving the requester is the guest who placed the order, letting unauthenticated remote attackers read order details and, where the PayPal plugin is active, reach PayPal create/capture flows for orders that are not theirs. The flaw sits in OrderRepo::getOrderByNumber, which returns a guest order (customer_id null) on the strength of the order_number argument alone; the CVSS 4.0 score is 6.9 with the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, so no credentials or user interaction are needed. Guest checkout must be in use on the target store and the attacker needs valid or guessable order numbers; a fix ships in 2.0.0.32 and no public exploit has been identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade to BeikeShop 2.0.0.32, which contains the getOrderByNumber/isGuestOrderAuthorized change and the getPayableOrder guard in the PayPal controller; the vendor advisory is at https://github.com/beikeshop/beikeshop/security/advisories/GHSA-p2x8-f9cm-m352 and the release at https://github.com/beikeshop/beikeshop/releases/tag/v2.0.0.32, with the fixing commit at https://github.com/beikeshop/beikeshop/commit/6cf25f8c15d27d1ff14a848faf645c94d20ba5f1. If upgrading immediately is not possible, the exposure can be narrowed by disabling guest checkout so that no orders with a null customer_id are created and the lookup path has nothing to return - the trade-off is that anonymous purchasing stops working entirely - and by deactivating the PayPal plugin, since the pre-patch PayPal create/capture handlers accept any order number and the fixed code gates that path on the plugin being active; the trade-off is loss of PayPal payments. Because the attack depends on supplying a valid order_number, tightening order-number generation and monitoring repeated lookups with sequential or unexpected numbers reduces the guessing window, but neither measure closes the missing authorization check, so upgrading remains the complete fix per the vendor.

Affected VersionsENISA

BeikeShop 2.0.0.0
BeikeShop 2.0.0.6
BeikeShop 2.0.0.23
BeikeShop 2.0.0.9
BeikeShop 2.0.0.3
BeikeShop 2.0.0.5
BeikeShop 2.0.0.24
BeikeShop 2.0.0.2
BeikeShop 2.0.0.4
BeikeShop 2.0.0.1
BeikeShop 2.0.0.31
BeikeShop 2.0.0.26
BeikeShop 2.0.0.28
BeikeShop 2.0.0.22
BeikeShop 2.0.0.12
BeikeShop 2.0.0.17
BeikeShop 2.0.0.8
BeikeShop 2.0.0.13
BeikeShop 2.0.0.29
BeikeShop 2.0.0.27
BeikeShop 2.0.0.16
BeikeShop 2.0.0.14
BeikeShop 2.0.0.10
BeikeShop 2.0.0.25
BeikeShop 2.0.0.20
BeikeShop 2.0.0.19
BeikeShop 2.0.0.7
BeikeShop 2.0.0.18
BeikeShop 2.0.0.30
BeikeShop 2.0.0.15
BeikeShop 2.0.0.11
BeikeShop 2.0.0.21

Affected Packages

euvd beikeshop no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

BeikeShop is a PHP e-commerce application built on Laravel, and the affected component is its guest order lookup repository. CWE-841 (improper enforcement of behavioral workflow) describes the root cause: the application's intended workflow is that a guest proves continuity with the session that created the order, but OrderRepo::getOrderByNumber($number, $customer) short-circuits that step and returns the order whenever a matching order_number is supplied. The upstream commit 6cf25f8c15d27d1ff14a848faf645c94d20ba5f1 adds OrderRepo::isGuestOrderAuthorized(), which rejects orders that have a customer_id, and for api/* requests compares a sha256 hash of the Bksessionid header against a cached guest_order.<number> value written at checkout, while web sessions must list the order number in session('guest_order_numbers'). The same commit routes the PayPal plugin's create, capture and nvpReturn handlers through a new getPayableOrder() helper that checks the paypal plugin is active, that the order's payment_method_code is paypal and status is unpaid, and that the caller is either the owning customer or an authorized guest. CPE data identifies the affected platform only as beikeshop (*) without enumerating versions, so the vulnerable range is taken from the advisory and commit history: releases up to and including 2.0.0.31.

Know when Beikeshop gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Unauthenticated remote access-control bypass of guest-order ownership gives AV:N/AC:L/PR:N/UI:N with C:L for exposed order data and I:L for limited order/payment-workflow abuse; no availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A security flaw has been discovered in BeikeShop up to 2.0.0.31. Impacted is the function OrderRepo::getOrderByNumber of the file beike/Repositories/OrderRepo.php of the component Guest Order Lookup. Performing a manipulation of the argument order_number results in enforcement of behavioral workflow. The attack can be initiated remotely. Upgrading to version 2.0.0.32 is recommended to address this issue. The patch is named 6cf25f8c15d27d1ff14a848faf645c94d20ba5f1. It is recommended to upgrade the affected component.

Threat Intelligence Overview

Prevalence
Low
open-source Laravel e-commerce platform with niche, non-enterprise deployment base
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy