iPaymu Payment Gateway for WooCommerce <= 2.0.2 - Missing Authentication to Unauthenticated Payment Bypass and Order Information Disclosure
Strategic Overview
- Status
- Patched in 2.0.3
- Affected Plugin
- iPaymu Payment Gateway for WooCommerce
- Affected Version
<= 2.0.2- CVSS
- 8.2High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-0656
At a glance
CVE-2026-0656 is a high-severity Missing Authorization vulnerability in the iPaymu Payment Gateway for WooCommerce WordPress plugin, affecting versions <= 2.0.2. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.0.3; sites on affected versions should update now. Disclosed January 2026, reported by Teerachai Somprasong.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-862: Missing Authorization
iPaymu Payment Gateway for WooCommerce <= 2.0.2 carries this weakness at check_ipaymu_response, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For iPaymu Payment Gateway for WooCommerce the fix is 2.0.3: builds <= 2.0.2 are affected, anything from 2.0.3 onward is not.
Remediation
Update to version 2.0.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: iPaymu Payment Gateway for WooCommerce 2.0.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C