Epeken All Kurir for Woocommerce <= 2.1.2 - Unauthenticated Payment Bypass
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Epeken All Kurir for Woocommerce
- Affected Version
<= 2.1.2- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-16739
At a glance
CVE-2026-16739 is a medium-severity Missing Authorization vulnerability in the Epeken All Kurir for Woocommerce WordPress plugin, affecting versions <= 2.1.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Pedro Pinho.
Vulnerability Overview
The Epeken All Kurir for Woocommerce plugin for WordPress is vulnerable to Payment Bypass in all versions up to, and including, 2.1.2. 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-862: Missing Authorization
Reaching this weakness in Epeken All Kurir for Woocommerce <= 2.1.2 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for Epeken All Kurir for Woocommerce yet, so installs running <= 2.1.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Epeken All Kurir for Woocommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C