Quick answers
- Is CVE-2026-80340 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-80340 being exploited in the wild.
- How severe is CVE-2026-80340?
- Medium severity, with a CVSS score of 5.3, published 9 September 2026.
- Which products and versions are affected?
- Payment Plugins for PayPal Payment Plugins for PayPal WooCommerce before 2.0.26.
- Is there a fix for CVE-2026-80340?
- A patch was published on 2026-09-09: Fixed in version 2.0.26 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-80340 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-80340?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The plugin fails to validate the WooCommerce order key before embedding order objects into JavaScript configuration on the checkout order-pay page. This allows unauthenticated users to enumerate sequential order IDs (e.g., /checkout/order-pay/1/, /checkout/order-pay/2/, etc.) and extract the order_key secret from the page HTML source, despite WooCommerce displaying an "invalid order" error to the user interface. Armed with the disclosed order_key, an attacker can access the order-received endpoint with any order ID and receive the full customer-facing order view, exposing PII including customer name, email, billing address, shipping address, and order line items. No authentication, session cookies, or non-default configuration is required. The vulnerability is fixed in version 2.0.26.
Affected products
- Payment Plugins for PayPal Payment Plugins for PayPal WooCommerce before 2.0.26
Timeline
- 2026-09-07: disclosed
- 2026-09-09: advisory
- 2026-09-09: patched: Fixed in version 2.0.26