dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-0692

HIGH · 7.5 CVSS v3.1 Published 2026-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The BlueSnap Payment Gateway for WooCommerce plugin up to version 3.4.0 relies on WooCommerce's WC_Geolocation::get_ip_address() to validate IPN requests, which trusts user-controllable headers (X-Real-IP, X-Forwarded-For). This allows unauthenticated attackers to spoof whitelisted BlueSnap IP addresses via these headers and send forged IPN data to manipulate order statuses (paid, failed, refunded, or on-hold).

MitigationReplace user-controllable header-based IP detection with server-side IP validation (using $_SERVER['REMOTE_ADDR'] directly) and implement additional request validation (e.g., cryptographic verification of IPN payloads) to prevent spoofing attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify BlueSnap Payment Gateway for WooCommerce is installed
    Navigate to Plugins > Installed Plugins in WordPress admin and locate the BlueSnap Payment Gateway for WooCommerce plugin. Confirm it appears in the list.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed plugin version
    In the Plugins page, look for the version number listed under the BlueSnap plugin description. Compare it to the affected range: any version up to and including 3.4.0 is vulnerable.
    Affected if The installed version is 3.4.0 or lower.
  3. Inspect plugin IPN handling code
    Access the plugin files via file manager or FTP. Locate the IPN callback handler (typically in the main plugin file or a dedicated IPN handler class). Search for usage of WC_Geolocation::get_ip_address().
    Affected if The code uses WC_Geolocation::get_ip_address() for IP request validation, which relies on user-controllable headers.
  4. Confirm IPN endpoint is reachable
    Check if the plugin registers an IPN listener endpoint (commonly at /?bluesnap-ipn=handler or similar). Attempt a request to the endpoint or examine the plugin's rewrite rules.
    Affected if The plugin exposes an IPN endpoint that processes requests using the vulnerable IP detection method.

A user is affected if the BlueSnap Payment Gateway for WooCommerce plugin version 3.4.0 or lower is installed and active, and the plugin processes IPN requests using WC_Geolocation::get_ip_address() which trusts client-supplied headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace user-controllable header-based IP detection with server-side IP validation (using $_SERVER['REMOTE_ADDR'] directly) and implement additional request validation (e.g., cryptographic verification of IPN payloads) to prevent spoofing attacks.

Recommended fix Moderate confidence

Bluesnap Payment Gateway for WooCommerce version 3.4.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Bluesnap Payment Gateway for WooCommerce' plugin
  4. Click 'Update now' if an update is available, or manually update to version 3.4.1 or higher
  5. Verify the update completed successfully
  6. Test that IPN functionality still works correctly with legitimate BlueSnap notifications

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0692 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data