Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-124576 — Bilingual analysis and safe PoC for CVE-2026-124576, a BeikeShop PayPal payment bypass and guest-order IDOR, with source checks, offline logic model, and fix review. | Kitploit
Tools/GitHubGitHub/capivara-research/cve-2026-124576
Vulnerability AnalysisCode AnalysisExploitationWeb Application ExploitationWeb Security
GitHubcapivara-research/cve-2026-124576

CVE-2026-124576

Bilingual analysis and safe PoC for CVE-2026-124576, a BeikeShop PayPal payment bypass and guest-order IDOR, with source checks, offline logic model, and fix review.

View RepositoryWebsite
10 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    936
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    555
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    353
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    348
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    336
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    288

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-124576 — BeikeShop PayPal payment bypass and guest-order IDOR

English | Português do Brasil

CVE VulDB VulDB Submit GHSA Fixed License

Technical analysis, safe proof-of-concept material, an offline logic model, and reproducible source checks for a payment workflow vulnerability in BeikeShop's PayPal REST integration.

At a glance

FieldValue
ProductBeikeShop
Affected versions2.0.0.0 through 2.0.0.31
Audited revisionf41f3909c3dfbb4a8a0cfe39491dd805c7cf1f7a
PayPal plugin1.1.0
Fixed version2.0.0.32
Security fix6cf25f8
EndpointPOST /paypal/capture
ParameterspaypalOrderId, order_number
WeaknessesCWE-840, CWE-841, plus guest-order access-control failure
Required privilegeNone; guest checkout is supported
CVSS 3.17.3 High — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CVSS 4.06.9 Medium
ResearcherFernando Viana — Capivara Research

Executive summary

BeikeShop's default PayPal REST capture flow accepted a PayPal order identifier and a local BeikeShop order number supplied by the client. The application captured the PayPal transaction and treated status === COMPLETED as sufficient proof that the selected local order had been paid.

The vulnerable flow did not verify that:

  • the captured amount equaled the authoritative local order total;
  • the captured currency matched the order currency;
  • the PayPal order was created for the submitted BeikeShop order; or
  • an unauthenticated guest was authorized to act on the selected local order.

An attacker could pay a genuine low-value PayPal Sandbox order and submit its paypalOrderId with the number of an unrelated, higher-value BeikeShop order. The completed low-value transaction could cause the unrelated order to be marked PAID.

Broken security boundary

The defect breaks the server-side binding between the payment confirmed by PayPal and the local order whose state BeikeShop changes.

attacker creates a cheap local order
                |
                v
PayPal approves a genuine cheap payment
                |
                v
attacker combines the cheap paypalOrderId
with a different expensive order_number
                |
                v
guest lookup resolves the unrelated order
                |
                v
REST capture checks only COMPLETED
                |
                v
unrelated expensive order becomes PAID

The same plugin already contained the missing design pattern in its NVP/SOAP branch: validateNvpDetails() compared PayPal amount, currency, and invoice data with the local order. Equivalent validation was absent from the default REST path.

Preconditions and limits

The demonstrated chain requires:

  1. BeikeShop 2.0.0.31 or an earlier affected 2.0.0.x release;
  2. the PayPal plugin enabled in REST mode;
  3. guest checkout available;
  4. a genuine approved low-value PayPal transaction; and
  5. knowledge or discovery of a target local order number.

The original research established the chain through source review. It was not executed against a production PayPal merchant account and did not move real funds. The dynamic helper is restricted to an explicitly supplied local or authorized PayPal Sandbox environment and is dry-run by default.

Root cause

Client-controlled transaction and order identifiers

PaypalController::capture() read both identifiers from the request, resolved the local order, and invoked REST capture without a persisted binding between those objects:

$paypalOrderId = $data['paypalOrderId'];
$orderNumber   = $data['order_number'];
$order         = OrderRepo::getOrderByNumber($orderNumber, $customer);
$result        = $paypalService->paypalClient->capturePaymentOrder($paypalOrderId);

Status-only validation

The vulnerable REST success predicate reduced the provider response to:

return $status === 'COMPLETED';

It did not compare the capture amount, currency, custom_id, invoice number, or local total.

Guest lookup without proof of possession

OrderRepo::getOrderByNumber() added a customer restriction only when a logged-in customer existed:

if ($customerId) {
    $builder->where('customer_id', $customerId);
}

For a guest request, a plaintext order number could select the order. Numbers also used a date prefix and a five-digit rand() value, which is not a cryptographic authorization capability.

Vulnerable data flow

StageCode pathMissing control
RequestPaypalController::capture()Trusts both client identifiers
LookupOrderRepo::getOrderByNumber()No guest capability/session check
Provider actioncapturePaymentOrder()No local-order binding validation
DecisionPaypalService::isPaymentSuccessful()Accepts status without amount or currency
State changemarkOrderPaid()Applies one transaction to the selected order

Safe reproduction material

The poc/ directory contains:

  • check_source.py, a read-only vulnerable/fixed source classifier;
  • logic_model.py, an offline demonstration of the logic flaw;
  • request.http, a documented raw request template;
  • poc.sh, a dry-run-by-default PayPal Sandbox helper;
  • verify-source.sh, the original source verifier; and
  • a complete laboratory guide.

Offline demonstration

python3 poc/logic_model.py

This does not contact BeikeShop or PayPal. It compares status-only validation with the fixed binding, amount, and currency checks.

Source classification

python3 poc/check_source.py /path/to/beikeshop
Exit codeMeaning
0Fixed controls detected
1Vulnerable source pattern detected
2Invalid or inconclusive source tree

Containerized check

docker build -t cve-2026-124576 .
docker run --rm cve-2026-124576

The image inspects the official v2.0.0.31 source and treats detection of the expected vulnerable pattern as a successful regression demonstration.

Expected results

ReleaseGuest authorizationREST validationMismatched payment/order
<= 2.0.0.31Plain order number can resolve guest orderStatus-onlyUnrelated order may be marked paid
2.0.0.32+Session-bound authorizationBinding, amount, currency, capture validationRequest is rejected

Impact

Download Tool