Quick answers
- Is CVE-2026-42637 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42637 being exploited in the wild.
- How severe is CVE-2026-42637?
- Medium severity, with a CVSS score of 6.5, published 6 October 2026.
- Which products and versions are affected?
- PayPlug for WooCommerce 3.1.0 and earlier.
- Is there a fix for CVE-2026-42637?
- No fixed version is recorded yet. Until an official patch is released, use web application firewall rules or a WordPress security plugin with Patchstack to block exploitation attempts targeting the vulnerable settings endpoints. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-42637 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-42637?
- 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
Until an official patch is released, use web application firewall rules or a WordPress security plugin with Patchstack to block exploitation attempts targeting the vulnerable settings endpoints.
Technical details
The PayPlug for WooCommerce plugin version 3.1.0 and earlier contains a broken access control vulnerability (CWE-639) that allows unauthenticated attackers to modify plugin settings without authentication. The vulnerability is exploitable over the network and likely involves a missing capability check on settings update endpoints. No official patch is currently available.
Affected products
- PayPlug PayPlug for WooCommerce 3.1.0 and earlier
Timeline
- 2026-10-05: disclosed
- 2026-10-06: advisory