WordPress plugin · payplug
Is PayPlug for WooCommerce (Official) safe?
Safe on 3.1.1 or newer.
The current version, 3.1.1, is past every affected range on record (4 of 4 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 4
- High or critical
- 1
- Exploited
- none
- Current version
- 3.1.1
- Last updated
- Oct 20, 2026
- Active installs
- 4,000+
Every recorded flaw
- Oct 28, 2026PayPlug for WooCommerce (Official): Does not perform any capability or ownership check on a set of unauthenticated AJAX actions that operate on a caller-supplied order identifierCVE-2026-113813 · fixed in 3.1.1 · reported by WPScanMedium 6.5
- Oct 28, 2026PayPlug for WooCommerce (Official): Does not verify that the requester owns the WooCommerce order named in a payment requestCVE-2026-110292 · fixed in 3.1.1 · reported by WPScanMedium 6.5
- Oct 6, 2026Unauthenticated Settings Change in PayPlug for WooCommerce (Official) <= 3.1.0 versions.CVE-2026-42637 · affects up to 3.1.0 · reported by PatchstackMedium 6.5
- Oct 6, 2026Unauthenticated Broken Access Control in PayPlug for WooCommerce (Official) <= 3.1.0 versions.CVE-2026-39751 · affects up to 3.1.0 · reported by PatchstackHigh 7.5
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.