The Tamara Checkout WordPress plugin through 1.9.9.20 does not verify the order key, a nonce, or any capability on its public payment cancel/fail return URLs, changing a WooCommerce order's status based solely on an attacker-supplied numeric order id, so an unauthenticated attacker can cancel or fail arbitrary orders store-wide by enumerating ids (triggering downstream stock-release and notification side-effects).
CVE-2026-16962
Score 5.3 from GitHub Security Advisory published 2026-08-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 28(Track)EG Risk 28/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 21, 2026Tamara Checkout <= 1.9.9.20 – Unauthenticated Order Status Manipulation | CVE 2026-16962 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/e026c89e-83cc-452c-bfb9-2630f1ade284/Vendor Advisories for CVE-2026-16962(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 19× in last 7d / 29× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:53 UTCEG score recompute
- 2026-08-29 19:53 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 19:26 UTCGHSA enrichment
- 2026-08-27 18:19 UTCEG score recompute
- 2026-08-27 18:19 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 16:48 UTCGHSA enrichment
- 2026-08-26 15:40 UTCEG score recompute
- 2026-08-26 15:40 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 15:09 UTCEG score recompute
- 2026-08-25 15:09 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 14:41 UTCEG score recompute
- 2026-08-24 14:41 UTCGHSA enrichment
- 2026-08-23 14:14 UTCEG score recompute
- 2026-08-23 14:14 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 13:47 UTCEG score recompute
- 2026-08-22 13:47 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 13:20 UTCEG score recompute▲ 5.30
- 2026-08-21 13:20 UTCGHSA enrichment
Show 4 moreShow fewer
- 2026-08-21 13:19 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
- 2026-08-21 07:34 UTCNVD update
- 2026-08-21 06:20 UTCEG score recompute
- 2026-08-21 06:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-16962?
When was CVE-2026-16962 disclosed?
Is CVE-2026-16962 actively exploited?
What is the CVSS score of CVE-2026-16962?
How do I remediate CVE-2026-16962?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16962
Is Your Infrastructure Affected by CVE-2026-16962?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.