CVE-2026-39645
Received Received - Intake
Server-Side Request Forgery in GlobalPayments WooCommerce

Publication date: 2026-04-08

Last updated on: 2026-04-13

Assigner: Patchstack

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-08
Last Modified
2026-04-13
Generated
2026-05-07
AI Q&A
2026-04-08
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
global_payments global_payments_woocommerce to 1.18.0 (inc)
globalpayments woocommerce to 1.18.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-39645 is a Server-Side Request Forgery (SSRF) vulnerability found in the GlobalPayments WooCommerce WordPress plugin versions up to and including 1.18.0.

This vulnerability allows an unauthenticated attacker to make the affected website send arbitrary HTTP requests to domains controlled by the attacker.

By exploiting this flaw, the attacker could potentially access sensitive information from other services running on the same system as the website.

The vulnerability has a CVSS score of 5.4, indicating a low severity impact, and is classified under the OWASP Top 10 category A10: Server-Side Request Forgery (SSRF).

No official patch is currently available, and the vulnerability requires no privileges to exploit, making it accessible to unauthenticated attackers.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The Server-Side Request Forgery (SSRF) vulnerability in GlobalPayments WooCommerce allows an attacker to make arbitrary HTTP requests and potentially access sensitive information from other services on the same system. This exposure of sensitive information could lead to non-compliance with data protection standards such as GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access.

Since the vulnerability enables unauthenticated attackers to exploit the system, it increases the risk of data breaches, which are critical compliance concerns under regulations like GDPR and HIPAA. Organizations using the affected plugin should consider this vulnerability a risk to their compliance posture until a patch is available and applied.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability allows an unauthenticated attacker to cause the affected website to make arbitrary HTTP requests to attacker-controlled domains. Detection can involve monitoring outgoing HTTP requests from the server hosting the GlobalPayments WooCommerce plugin for unusual or unexpected destinations.

Since the vulnerability is in the GlobalPayments WooCommerce plugin versions up to 1.18.0, first verify the plugin version installed on your WordPress site.

  • Check the plugin version via WordPress admin dashboard or by running: wp plugin list | grep global-payments-woocommerce
  • Monitor outgoing HTTP requests from the server using network tools such as tcpdump or Wireshark to detect suspicious requests to unknown domains.
  • Use command line tools like curl or wget to test if the plugin endpoint is vulnerable by attempting SSRF payloads (only in a controlled and authorized environment).
  • Example command to check plugin version: wp plugin list | grep global-payments-woocommerce
  • Example tcpdump command to monitor HTTP requests: sudo tcpdump -i eth0 -A 'tcp port 80 or tcp port 443'

How can this vulnerability impact me? :

Exploiting this SSRF vulnerability could allow an attacker to make the affected website perform arbitrary HTTP requests to attacker-controlled domains.

This could lead to unauthorized access to sensitive information from other services running on the same system as the website.

Since the vulnerability requires no authentication, it can be exploited by anyone, increasing the risk of mass-exploit campaigns targeting multiple websites.

However, the overall severity is considered low, so while the impact is limited, it still poses a security risk that should be addressed.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation involves updating the GlobalPayments WooCommerce plugin once a patch is released.

Until an official patch is available, seek assistance from your hosting providers or web developers to implement temporary protections.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart