Quick answers
- Is CVE-2026-113813 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113813 being exploited in the wild.
- How severe is CVE-2026-113813?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- PayPlug for WooCommerce 2.8.0 through 3.1.0.
- Is there a fix for CVE-2026-113813?
- Yes: fixed in 3.1.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113813 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113813?
- Check whether you run PayPlug for WooCommerce 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.
How to fix
- Fixed in: 3.1.1
Technical details
The plugin fails to implement capability and ownership checks on unauthenticated AJAX actions that process order identifiers supplied by the caller. An attacker can directly invoke these AJAX endpoints with arbitrary order IDs to perform unauthorized actions (modification, deletion, disclosure). This is an insecure direct object reference (IDOR) vulnerability with network attack vector requiring no authentication or user interaction.
Affected products
- PayPlug PayPlug for WooCommerce 2.8.0 through 3.1.0
Timeline
- 2026-10-26: disclosed
- 2026-10-28: patched: Fixed in version 3.1.1