# CVE-2026-16739: Epeken All Kurir <= 2.1.4 - Unauthenticated Order Payment Confirmation Forgery

> Unauthenticated attackers can forge payment confirmations to mark arbitrary orders as confirmed, potentially bypassing payment verification in this WooCommerce plugin.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-wqwq-hmg7-q93r

## What is CVE-2026-16739?

CVE-2026-16739 is a medium-severity missing authorization vulnerability in Unknown Epeken All Kurir for Woocommerce, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Epeken All Kurir for Woocommerce WordPress plugin through 2.1.4 does not verify that a payment-confirmation request originates from the owner of the targeted order, nor that any payment actually occurred, allowing unauthenticated attackers to mark arbitrary orders as confirmed and, in a non-default configuration, paid.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-16739?


## How do I fix CVE-2026-16739?

No fix has been published for CVE-2026-16739 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16739 being exploited?

There is no known exploitation of CVE-2026-16739 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16739 and fix it if it is affected.

What it is: CVE-2026-16739 is a medium-severity missing authorization vulnerability in Unknown Epeken All Kurir for Woocommerce, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16739 in the wild and no public exploit code.

Affected product: Unknown Epeken All Kurir for Woocommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16739/ (Markdown: https://insights.sbomify.com/CVE-2026-16739/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16739
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16739
- OSV: https://osv.dev/vulnerability/CVE-2026-16739

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16739/
Summaries are generated and may contain mistakes; the official description above is the record.