BlueSnap Payment Gateway for WooCommerce <= 3.4.0 - Missing Authorization to Unauthenticated Arbitrary Order Status Manipulation
Strategic Overview
- Status
- Patched in 3.4.1
- Affected Plugin
- BlueSnap Payment Gateway for WooCommerce
- Affected Version
<= 3.4.0- CVSS
- 7.5High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-0692
At a glance
CVE-2026-0692 is a high-severity Missing Authorization vulnerability in the BlueSnap Payment Gateway for WooCommerce WordPress plugin, affecting versions <= 3.4.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.4.1; sites on affected versions should update now. Disclosed February 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).
Vulnerability Overview
The BlueSnap Payment Gateway for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.4.0. This is due to the plugin relying on WooCommerce's `WC_Geolocation::get_ip_address()` function to validate IPN requests, which trusts user-controllable headers like X-Real-IP and X-Forwarded-For to determine the client IP address. This makes it possible for unauthenticated attackers to bypass IP allowlist restrictions by spoofing a whitelisted BlueSnap IP address and send forged IPN (Instant Payment Notification) data to manipulate order statuses (mark orders as paid, failed, refunded, or on-hold) without proper authorization.
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 integrity.
CWE-862: Missing Authorization
BlueSnap Payment Gateway for WooCommerce <= 3.4.0 carries this weakness at get_ip_address(), 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 BlueSnap Payment Gateway for WooCommerce the fix is 3.4.1: builds <= 3.4.0 are affected, anything from 3.4.1 onward is not.
Remediation
Update to version 3.4.1, 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: BlueSnap Payment Gateway for WooCommerce 3.4.1 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