dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-39645

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
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
Server-Side Request Forgery (SSRF) vulnerability in Global Payments GlobalPayments WooCommerce global-payments-woocommerce allows Server Side Request Forgery.This issue affects GlobalPayments WooCommerce: from n/a through <= 1.18.0.

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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in the GlobalPayments WooCommerce plugin versions <= 1.18.0 allows remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources by manipulating input parameters used in server-side request functions.

MitigationUpdate to the patched version of the GlobalPayments WooCommerce plugin (if available) or implement URL allowlist validation on any user-controlled input used in server-side requests to prevent requests to unauthorized destinations.

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/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. Locate the GlobalPayments WooCommerce plugin
    Access your WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'GlobalPayments' or check for a payment gateway plugin from Global Payments. Alternatively, check your wp-content/plugins directory for a folder named 'globalpayments-gateway-woocommerce' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find the GlobalPayments plugin and note the version number displayed. Alternatively, check the main plugin PHP file for the 'Version' header comment.
    Affected if The version is 1.18.0 or lower
  3. Verify the plugin is active and configured
    In WordPress admin, go to WooCommerce > Settings > Payments (or Payments > Gateways) and check if any GlobalPayments gateway is installed and enabled. An SSRF attack requires the plugin to be active and configured as a payment option.
    Affected if The plugin is active with a GlobalPayments payment gateway enabled

You are affected if the GlobalPayments WooCommerce plugin version 1.18.0 or lower is installed, active, and configured as a payment gateway in your WooCommerce store.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the patched version of the GlobalPayments WooCommerce plugin (if available) or implement URL allowlist validation on any user-controlled input used in server-side requests to prevent requests to unauthorized destinations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39645 — 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-39645 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