CVE-2018-20782: The GloBee plugin before 1.1.2 for WooCommerce mishandles IPN messages.

Q: How do I fix CVE-2018-20782?

woocommerce: upgrade to 1.1.2. Exact commands for each OS are on this page.

Q: Is CVE-2018-20782 being exploited?

CVE-2018-20782 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-20782 affect?

CVE-2018-20782 affects woocommerce. Severity is high (CVSS 7.5). The GloBee plugin before 1.1.2 for WooCommerce mishandles IPN messages.

Q: How urgent is CVE-2018-20782?

Priority 60/100. High severity; EPSS top 4%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2018-20782 is a high-severity flaw (CVSS 7.5) affecting woocommerce. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The GloBee plugin before 1.1.2 for WooCommerce mishandles IPN messages.

Why this priority

High severity
EPSS top 4%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	10.0% (top 4%)
CISA exploited list	No
Weakness	CWE-20
Published	2019-02-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: globee

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-02-17 18:29 UTCPublished CVE record published
2026-06-17 01:53 UTCUpdated Record last modified

globee woocommerce UPGRADE

Affected: < 1.1.2

Fixed in: 1.1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy woocommerce || rpm -q woocommerce || woocommerce --version

2. UPGRADE to 1.1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade woocommerce

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade woocommerce

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: WordPress Plugin WooCommerce - GloBee (cryptocurrency) Payment Gateway 1.1.1 - Payment Bypass / Unauthorized Order Statu

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-20782?

woocommerce: upgrade to 1.1.2. Exact commands for each OS are on this page.

Is CVE-2018-20782 being exploited?

CVE-2018-20782 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-20782 affect?

CVE-2018-20782 affects woocommerce. Severity is high (CVSS 7.5). The GloBee plugin before 1.1.2 for WooCommerce mishandles IPN messages.

How urgent is CVE-2018-20782?

Priority 60/100. High severity; EPSS top 4%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WooCommerce vulnerabilities

Related CVEs

CVE-2024-1310 MEDIUM 4.9 UPGRADE The WooCommerce WordPress plugin before 8.6 does not prevent users with at least the contributor role from lea
CVE-2025-5062 MEDIUM 6.1 UPGRADE The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customiz
CVE-2024-9944 MEDIUM 5.3 UPGRADE The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0
CVE-2024-37297 MEDIUM 5.4 UPGRADE WooCommerce is an open-source e-commerce platform built on WordPress
CVE-2023-52222 MEDIUM 4.3 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in Automattic WooCommerce.This issue affects WooCommerce: from

References

← Back to latest CVEs