CVE-2026-88928: PAYCOMET for WooCommerce (WordPress plugin) · Improper Authentication
Affects PAYCOMET for WooCommerce (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 5.46 soon.
Data as of 29 Oct 2026, 07:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 5.46
Exploitation evidence
Disclosed: evidence found.
CVE published 29 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 29 Oct 2026.
What to do
Upgrade PAYCOMET for WooCommerce (WordPress plugin) to 5.46.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PAYCOMET for WooCommerce | Affected
| Fixed in
|
AI-suggested
Upgrade PAYCOMET for WooCommerce to version 5.46 or later, where the cryptographic signature verification on the payment notification endpoint is properly implemented, mitigating this authentication vulnerability.
Description
PAYCOMET for WooCommerce versions from 5.36 up to but not including 5.46 contain an authentication flaw where the plugin does not verify the cryptographic signature on payment notification requests related to tokenisation. This allows unauthenticated attackers to overwrite stored payment tokens for existing orders and delete saved card records. The issue is fixed in version 5.46.