BeikeShop Guest Order Lookup OrderRepo.php getOrderByNumber behavioral workflow
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.31% · 24th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 46/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
BeikeShop, up to version 2.0.0.31, has a flaw in its Guest Order Lookup feature that lets an attacker manipulate the order number input to bypass the intended order-lookup workflow. The attacker can exploit this remotely, without logging in or any user action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 51 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- Exploit code on GitHub
capivara-research/CVE-2026-124576
Affected versions
- n/a BeikeShop
2.0.0.0, 2.0.0.1, 2.0.0.2, 2.0.0.3, 2.0.0.4, 2.0.0.5, 2.0.0.6, 2.0.0.7, 2.0.0.8, 2.0.0.9, 2.0.0.10, 2.0.0.11, 2.0.0.12, 2.0.0.13, 2.0.0.14, 2.0.0.15, 2.0.0.16, 2.0.0.17, 2.0.0.18, 2.0.0.19, 2.0.0.20, 2.0.0.21, 2.0.0.22, 2.0.0.23, 2.0.0.24, 2.0.0.25, 2.0.0.26, 2.0.0.27, 2.0.0.28, 2.0.0.29, and 2 more
Evidence 9
- Advisory
- Advisory
- Advisory
- Advisory
- Advisory
Show all 9 sourcesShow fewer sources
- Patch
- Patch
- Exploit
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124576
Is CVE-2026-124576 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
Which versions are affected by CVE-2026-124576?
BeikeShop: versions 2.0.0.0, 2.0.0.1, 2.0.0.2, 2.0.0.3, 2.0.0.4 and 27 more.Source: cve.now feed data