CVE-2026-39751: PayPlug for WooCommerce broken access control

CVE-2026-39751 · Severity: high · CVSS 7.5 · Published 2026-10-06

PayPlug for WooCommerce is a payment plugin for online stores built on WordPress. An unauthenticated attacker can bypass access controls to gain unauthorized access to payment or store functionality, potentially exposing sensitive data or enabling fraud.

Technologies: PayPlug for WooCommerce. Vendors: PayPlug.

Quick answers

Is CVE-2026-39751 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-39751 being exploited in the wild.
How severe is CVE-2026-39751?
High severity, with a CVSS score of 7.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-39751?
No fixed version is recorded yet. Check the vendor's advisory in the references below. 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-39751 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-39751?
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.

Technical details

The plugin versions 3.1.0 and earlier contain a broken access control vulnerability that can be exploited without authentication. The flaw allows attackers to access restricted functions or data by crafting unauthorized requests, likely through unprotected API endpoints or admin actions that lack proper permission checks.

Affected products

  • PayPlug PayPlug for WooCommerce 3.1.0 and earlier

Timeline

  • 2026-10-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.