Skip to content
Laskyr

CVE-2026-86791: iPOSpays Payment Gateway for WooCommerce vulnerability

medium 5.3 published 2026-10-19

Fixed in iPOSpays Payment Gateway for WooCommerce 1.4.7

iPOSpays Payment Gateway for WooCommerce older than 1.4.7 is affected by this security issue. Sites on 1.4.7 or newer are not affected; the latest release is 1.4.7.

Affected versions
older than 1.4.7
Fixed in
1.4.7
Latest version
1.4.7
Severity
Medium · CVSS 5.3
Active installs
200+
Type
Security issue

What an attacker needs

CVSS vector (score by WPScan): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What to do now

  1. Update iPOSpays Payment Gateway for WooCommerce to 1.4.7 or newer: Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. Not sure which version you run? Check your version against every known iPOSpays Payment Gateway for WooCommerce issue. With WP-CLI: wp plugin get ipospays-gateways-wc --field=version.
  5. If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.

The advisory

The iPOSpays Payment Gateway for WooCommerce WordPress plugin before 1.4.7 does not verify that a payment was actually completed before recording an order as paid, allowing unauthenticated users to mark any unpaid order as paid and to rewrite its total.

Description from the CVE record, published by WPScan (the CVE Numbering Authority), via the NVD entry for CVE-2026-86791.

References

Related

Ran an affected version? Check your site for signs of a hack

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Where this data comes from

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit