CVE-2026-94361VulnerabilityPublished 31 Oct 2026

The Payable Payment Gateway for WooCommerce WordPress plugin before 1.3.1 does not verify the authenticity of an

Source GCVE Database

Compare

Authoritative record:CVE-2026-94361· High

Not known to be exploited : upgrade to 1.3.1 soon.

Data as of 31 Oct 2026, 07:08 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 1.3.1

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-x7hw-7xvr-75fq

What to do

Upgrade Payable Payment Gateway for WooCommerce (WordPress plugin) to 1.3.1.

Affected software

Product	Affected	Fixed in
Payable Payment Gateway for WooCommerce	Affected <1.3.1	Fixed in 1.3.1

AI-suggested

Upgrade the Payable Payment Gateway for WooCommerce plugin to version 1.3.1 or later, where the issue has been fixed. No other mitigation guidance is provided, so applying the official update is the recommended action.

Description

The Payable Payment Gateway for WooCommerce WordPress plugin versions before 1.3.1 fails to verify the authenticity of incoming payment notifications. This flaw allows unauthenticated attackers to alter the payment status of any order in the store, regardless of the payment method used.

Impact

Unauthenticated attackers can change the payment status of any WooCommerce order in stores using the vulnerable plugin versions. This can lead to financial discrepancies, unauthorized order fulfillment, or denial of legitimate payments.

Summary

The vulnerability in the Payable Payment Gateway for WooCommerce WordPress plugin prior to version 1.3.1 involves a lack of verification for incoming payment notifications. Without authenticating these notifications, attackers can manipulate order payment statuses to paid or failed arbitrarily. This affects all orders processed through the plugin, potentially leading to fraudulent order status changes.

References

Community reviews

Loading reviews…