CVE-2026-16739

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-08-14. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Epeken All Kurir for Woocommerce WordPress plugin through 2.1.2 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.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 14, 2026

Last Modified

August 14, 2026

Advisory Details (1)

Auto-updated Aug 14, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Epeken All Kurir <= 2.1.2 – Unauthenticated Order Payment Confirmation Forgery | CVE 2026-16739 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/b66b86f9-e49e-4654-84a1-0f2e5c859289/

Vendor Advisories for CVE-2026-16739(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 02:33 UTCEG score recompute
  2. 2026-08-21 02:33 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 04:32 UTCEG score recompute
  5. 2026-08-20 04:32 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 06:32 UTCEG score recompute
  8. 2026-08-19 06:32 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 08:32 UTCEG score recompute
  11. 2026-08-18 08:32 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 10:30 UTCEG score recompute
  14. 2026-08-17 10:30 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 12:31 UTCEG score recompute
  17. 2026-08-16 12:31 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 14:31 UTCEG score recompute
  20. 2026-08-15 14:31 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 16:31 UTCGHSA enrichment
  23. 2026-08-14 16:04 UTCEG score recompute▲ 5.90
  24. 2026-08-14 16:04 UTCGHSA enrichment
  25. 2026-08-14 16:03 UTCMITRE cvelistV5CVSS v3 → 5.9 · severity → MEDIUM
Show 3 more
  1. 2026-08-14 06:26 UTCNVD update
  2. 2026-08-14 06:09 UTCEG score recompute
  3. 2026-08-14 06:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16739?
CVE-2026-16739 is a medium vulnerability published on August 14, 2026. The Epeken All Kurir for Woocommerce WordPress plugin through 2.1.2 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…
When was CVE-2026-16739 disclosed?
CVE-2026-16739 was first published in the National Vulnerability Database on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16739 actively exploited?
CVE-2026-16739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.1% of all scored CVEs.
What is the CVSS score of CVE-2026-16739?
CVE-2026-16739 has a CVSS v3.1 base score of 5.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16739?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16739, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16739

Explore →

Is Your Infrastructure Affected by CVE-2026-16739?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs