PayPlug for WooCommerce (Official)
payplug · plugin
Known security vulnerabilities for PayPlug for WooCommerce (Official). Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
4 exploitable without logging in · latest Oct 28, 2026
Before you install
Use with care
- 4 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 3.1.1 · last updated Oct 20, 2026 · 4K+ installs
wordpress.org status checked on Nov 5, 2026
Vulnerabilities
- High 7.5
CVE-2026-39751unauthenticated≤ 3.1.0
WordPress PayPlug for WooCommerce (Official) plugin <= 3.1.0 - Broken Access Control vulnerability
- Medium 6.5
CVE-2026-113813unauthenticated→ 3.1.1
PayPlug for WooCommerce 2.8.0 - 3.1.0 - Unauthenticated Arbitrary Order Deletion, Modification and Disclosure
- Medium 6.5
CVE-2026-110292unauthenticated→ 3.1.1
PayPlug for WooCommerce 2.9.0 - 3.1.0 - Unauthenticated Order Key Disclosure and Order Cancellation via payplug_create_intent
- Medium 6.5
CVE-2026-42637unauthenticated≤ 3.1.0
WordPress PayPlug for WooCommerce (Official) plugin <= 3.1.0 - Settings Change vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).