The Payex Payment Gateway for Woocommerce WordPress plugin through 1.2.10 does not properly verify the authenticity of
Source GCVE Database
Not known to be exploited.
Data as of 27 Oct 2026, 07:44 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 27 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 |
|---|---|---|
| Payex Payment Gateway for Woocommerce | Affected
| Fixed in– |
AI-suggested
Users should verify if a patch has been released by the vendor. Until then, it is recommended to configure a non-empty validation secret for payment notifications to ensure authenticity verification. Monitor the vendor advisory for updates and apply any official fixes once available.
Description
The Payex Payment Gateway for Woocommerce WordPress plugin versions through 1.2.10 fails to properly verify the authenticity of incoming payment notifications. This is due to reliance on a validation secret that is empty by default, which allows unauthenticated attackers to forge payment confirmations and mark orders as paid without authorization.