Quick answers
- Is CVE-2026-12973 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12973 being exploited in the wild.
- How severe is CVE-2026-12973?
- Informational severity, with a CVSS score of 6.5, published 20 July 2026.
- Which products and versions are affected?
- PayPlus Payment Gateway < 8.2.2.
- Is there a fix for CVE-2026-12973?
- A patch was published on 2026-08-22: Fixed in version 8.2.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-12973 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-12973?
- Check whether you run PayPlus Payment Gateway at an affected version. 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 PayPlus Payment Gateway plugin fails to implement proper authorization checks and order-ownership validation within the 'complete_order' AJAX action. An unauthenticated attacker can trigger this action by providing a valid 'frontNonce' (which is publicly accessible on the checkout page) and a target 'order_id'. Because order IDs are typically sequential, an attacker can enumerate orders to disclose their secret WooCommerce order keys via the 'redirect_url' in the JSON response. Furthermore, if an order has an existing successful PayPlus response but hasn't reached the final success state, this request can force a status transition (e.g., from 'pending' to 'processing') without valid payment verification. The issue is fixed in version 8.2.2.
Affected products
- PayPlus PayPlus Payment Gateway < 8.2.2
Timeline
- 2026-06-29: disclosed: Publicly published by WPScan
- 2026-07-20: advisory: NVD publication date
- 2026-08-22: patched: Fixed in version 8.2.2