Skip to content
Laskyr

Plugins · bluesnap-payment-gateway-for-woocommerce · data as of 2026-11-04

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

No known unpatched vulnerabilities in the latest version (3.4.5)

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

Latest version
3.4.5
Last updated
2026-09-01
Active installs
90+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 8.2+

Accept cards, ACH, Apple Pay and Google Pay, along with support for WooCommerce Subscriptions and Pre-orders on a global payments gateway. — by Scott Ring

What to do

  1. Update to the latest version (3.4.5). Anything older than 3.4.1 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 bluesnap-payment-gateway-for-woocommerce --field=version shows what you run; wp plugin update bluesnap-payment-gateway-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 7.5 CVE-2026-0692 · published 2026-02-14

Missing authorization check in BlueSnap Payment Gateway for WooCommerce (3.4.0 and older)

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

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.

NVD CVE-2026-0692Wordfence advisoryPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
BlueSnap Payment Gateway for WooCommerce vulnerability status badge
<a href="https://laskyr.com/plugins/bluesnap-payment-gateway-for-woocommerce"><img src="https://laskyr.com/plugins/bluesnap-payment-gateway-for-woocommerce/badge.svg" alt="BlueSnap 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