New from Wiz Research: Critical NGINX flaw. Understand the risk and impact.
Vulnerability DatabaseGHSA-vrxr-rp64-42vq

GHSA-vrxr-rp64-42vq: 
PHP vulnerability analysis and mitigation

Summary

In stores where "Checkout Success" is set to "standard" and "Invoice Close Handling" is set to "keep order", an unauthenticated visitor can bind another customer's unpaid order to their own checkout session through the Pay endpoint. From there they can read that order's billing name, email and address, and change the order's status. Stores using the default settings are not affected.

Details

Controller/Invoice/Pay.php accepts an order_id and an invoice_id from the request. It loads the order and checks that the BitPay invoice is in the "new" state, but it does not check that the invoice belongs to that order, or that the order belongs to the current session. It then sets the order as the last order of the visitor's checkout session. After that, the checkout success page runs Model/BPRedirect.php for the session's last order. It writes the order's billing address and customer email into the session as customer_info, changes the order status and creates a new BitPay invoice for it. Controller/Customer/Data.php returns customer_info as JSON. An attacker can use a "new" invoice from their own order together with another customer's order ID. Order entity IDs are sequential, so they are easy to guess. The fix in 10.2.5 makes the Pay endpoint check that the order is the last order placed in the current session, that the invoice is stored for that order, and that BitPay reports the same order ID for the invoice.

Proof of concept

Requirements: Checkout Success = standard, Invoice Close Handling = keep order.

  1. As the attacker, place an order with BitPay and keep its invoice in the "new" state (do not pay it). Note the invoice ID.
  2. Guess the entity ID of another customer's unpaid BitPay order.
  3. Open /bitpay-invoice/invoice/pay?order_id=VICTIM_ORDER_ID&invoice_id=ATTACKER_INVOICE_ID. The victim's order becomes the last order of the attacker's session.
  4. Open /checkout/onepage/success. The plugin loads the victim's order, stores its billing data in the session and creates a new invoice for it.
  5. Open /bitpay-invoice/customer/data. The response contains the victim's billing name, email and address.

Impact

Exposure of other customers' personal data (billing name, email and full address) and unauthorized changes to their orders (status change and a new BitPay invoice). Only stores that changed both settings above are affected. No payment can be marked as paid through this issue.


Source: NVD

Related PHP vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

GHSA-mm3h-q67x-4779HIGH7.4
  • PHP logoPHP
  • flipboxfactory/saml-sp
NoYesNov 18, 2026
CVE-2026-63389MEDIUM5
  • PHP logoPHP
  • awcodes/filament-curator
NoYesNov 17, 2026
GHSA-vrxr-rp64-42vqMEDIUM4.8
  • PHP logoPHP
  • bitpay/module-bpcheckout
NoYesNov 17, 2026
GHSA-58h6-g9mx-7ffrLOWN/A
  • PHP logoPHP
  • hengstverzeichnis/framework
NoYesNov 18, 2026
GHSA-xc2j-7c2r-wjjvMEDIUMN/A
  • PHP logoPHP
  • zumba/json-serializer
NoYesNov 17, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management