Skip to content
Laskyr

Plugins · ipaymu-for-woocommerce · data as of 2026-11-04

Is iPaymu Payment Gateway for WooCommerce safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.0.3)

As of 2026-11-04. 1 issue is on record for older versions; version 2.0.3 or newer fixes all of them that state a fix.

Latest version
2.0.3
Last updated
2025-12-30
Active installs
100+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
6.9.11 · PHP 7.4+

iPaymu Payment Gateway for WooCommerce enables secure payments via Virtual Account, QRIS, Minimarket, Credit Card, and Direct Debit in Indonesia. — by iPaymu

What to do

  1. Update to the latest version (2.0.3). Anything older than 2.0.3 has at least one known issue listed below. 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. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get ipaymu-for-woocommerce --field=version shows what you run; wp plugin update ipaymu-for-woocommerce updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 8.2 CVE-2026-0656 · published 2026-01-07

Missing authorization check in iPaymu Payment Gateway for WooCommerce (2.0.2 and older)

Affected
2.0.2 and older
Fixed in
2.0.3 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The iPaymu Payment Gateway for WooCommerce plugin for WordPress is vulnerable to Missing Authentication in all versions up to, and including, 2.0.2 via the 'check_ipaymu_response' function. This is due to the plugin not validating webhook request authenticity through signature verification or origin checks. This makes it possible for unauthenticated attackers to mark WooCommerce orders as paid by sending crafted POST requests to the webhook endpoint without any payment occurring, as well as enumerate order IDs and obtain valid order keys via GET requests, exposing customer order PII including names, addresses, and purchased products.

NVD CVE-2026-0656Wordfence advisoryCode change (fix)Plugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
iPaymu Payment Gateway for WooCommerce vulnerability status badge
<a href="https://laskyr.com/plugins/ipaymu-for-woocommerce"><img src="https://laskyr.com/plugins/ipaymu-for-woocommerce/badge.svg" alt="iPaymu Payment Gateway for WooCommerce vulnerability status"></a>

← Check another plugin · Free hacked-site scan

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