PAYCOMET for WooCommerce 5.36 - 5.45 - Unauthenticated Payment Bypass
Strategic Overview
- Status
- Patched in 5.46
- Affected Plugin
- PAYCOMET for WooCommerce
- Affected Version
5.36 – 5.45- CVSS
- 5.3Medium
- Weakness type
- CWE-602 · Client-Side Enforcement of Server-Side Security
- CVE
CVE-2026-88928
At a glance
CVE-2026-88928 is a medium-severity Client-Side Enforcement of Server-Side Security vulnerability in the PAYCOMET for WooCommerce WordPress plugin, affecting versions 5.36 – 5.45. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.46; sites on affected versions should update now. Disclosed October 2026, reported by JunHee CHO.
Vulnerability Overview
The PAYCOMET for WooCommerce plugin for WordPress is vulnerable to Payment Bypass in versions 5.36 through 5.45. This is due to a lack of server-side payment verification. This makes it possible for unauthenticated attackers to bypass payments.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-602: Client-Side Enforcement of Server-Side Security
The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.
Remediation
Update to version 5.46, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: PAYCOMET for WooCommerce 5.46 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in PAYCOMET for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C