The UniPAY Payment Gateway For WooCommerce WordPress plugin through 2.3 does not properly verify the authenticity of
Source GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 07:29 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| UniPAY Payment Gateway For WooCommerce | Affected
| Fixed in– |
AI-suggested
Users should verify and configure a non-empty merchant secret to ensure proper signature verification. Monitor the vendor advisory for any forthcoming patches or official guidance.
Description
The UniPAY Payment Gateway for WooCommerce WordPress plugin versions up to 2.3 does not properly verify payment notification authenticity. The plugin checks notification signatures against a merchant secret that is empty by default, enabling attackers to forge valid notifications and mark arbitrary orders as paid.