# CVE-2026-124576: BeikeShop Guest Order Lookup OrderRepo.php getOrderByNumber behavioral workflow


- **Severity:** Medium 6.9 (`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/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-5655-hp8h-9ffj, GHSA-p2x8-f9cm-m352

## What is CVE-2026-124576?

CVE-2026-124576 is a medium-severity vulnerability in BeikeShop, published on 9 Nov 2026. 

### Official 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.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow), CWE-840

## Which versions are affected by CVE-2026-124576?


## How do I fix CVE-2026-124576?

No fix has been published for CVE-2026-124576 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124576 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124576 exists.

Public exploit code:

- CVE-2026-124576: BeikeShop PayPal payment bypass and guest-order IDOR — bilingual analysis and safe PoC (github_poc): https://github.com/capivara-research/CVE-2026-124576

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124576 and fix it if it is affected.

What it is: CVE-2026-124576 is a medium-severity vulnerability in BeikeShop, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124576 exists.

Affected product: BeikeShop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124576/ (Markdown: https://insights.sbomify.com/CVE-2026-124576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124576
- OSV: https://osv.dev/vulnerability/CVE-2026-124576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124576/
Summaries are generated and may contain mistakes; the official description above is the record.