# CVE-2026-83533: WP Express Checkout payment verification bypass

Source: https://junglewise.ai/threats/cve-2026-83533-wp-express-checkout-payment-verification-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-02. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-83533 · Severity: medium · CVSS 5.3 · Published 2026-09-02

The WP Express Checkout WordPress plugin fails to verify payments server-side before marking orders as paid. An attacker can forge a fake completed payment and claim a digital product without actually paying, allowing free access to paid downloads and undermining e-commerce revenue for site operators.

Technologies: [WP Express Checkout](https://junglewise.ai/threats/technologies/wp-express-checkout). Vendors: [WP Express Checkout](https://junglewise.ai/threats/vendors/wp-express-checkout).

## Quick answers

**Is CVE-2026-83533 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-83533 being exploited in the wild.

**How severe is CVE-2026-83533?** Medium severity, with a CVSS score of 5.3, published 2 September 2026.

**Which products and versions are affected?** WP Express Checkout before 2.4.9.

**Is there a fix for CVE-2026-83533?** A patch was published on 2026-09-02: Fixed in version 2.4.9 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-83533 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-83533?** Check whether you run WP Express Checkout 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

This is a server-side request forgery (SSRF) and authentication bypass vulnerability in the plugin's wpec_process_payment AJAX endpoint. The vulnerable component does not verify that a payment gateway (PayPal) actually processed a transaction before accepting payment status from the client. An unauthenticated attacker can extract the nonce, product ID, and price from the public product page, then submit a forged POST request with status=COMPLETED and arbitrary transaction details. The plugin accepts the fake payment and creates a paid order post without contacting the payment gateway, granting access to the digital product. No user interaction or authentication is required; the attack succeeds against any WP Express Checkout installation with a published product. Versions before 2.4.9 are vulnerable; a patch is available.

## Affected products

- WP Express Checkout WP Express Checkout before 2.4.9

## Timeline

- 2026-09-01: disclosed
- 2026-09-02: patched: Fixed in version 2.4.9

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://wpscan.com/vulnerability/8ffb76d6-fda5-4819-ab07-d8c086169110/](https://wpscan.com/vulnerability/8ffb76d6-fda5-4819-ab07-d8c086169110/)

## Related threats

- [WP Express Checkout broken access control vulnerability](https://junglewise.ai/threats/cve-2026-96818-unauthenticated-broken-access-control-in-wp-express-checkout)
- [WP Express Checkout payment verification bypass](https://junglewise.ai/threats/cve-2026-83537-wp-express-checkout-payment-verification-bypass)