CVE-2026-16947

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

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

The Total processing card payments for WooCommerce WordPress plugin through 7.3 does not validate a user-supplied path before using it to build a server-side verification request, and does not verify the authenticity of the response, allowing unauthenticated attackers to redirect that request to an arbitrary host (disclosing the merchant's payment-gateway credentials) and to forge a success response that marks arbitrary WooCommerce orders as paid.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 29, 2026

Last Modified

August 30, 2026

Advisory Details (1)

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

Total Processing Card Payments for WooCommerce <= 7.3 – Unauthenticated SSRF leading to Payment Bypass and Gateway Credential Disclosure | CVE 2026-16947 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/53fe46b3-e8c4-448e-aa80-b7fb02fffa51/

Vendor Advisories for CVE-2026-16947(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 11× in last 7d / 11× 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-30 05:25 UTCEG score recompute
  2. 2026-08-30 05:25 UTCGHSA enrichment
  3. 2026-08-30 01:29 UTCEG score recompute
  4. 2026-08-30 01:29 UTCGHSA enrichment
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-30 01:09 UTCEG score recompute▲ 9.10
  7. 2026-08-30 01:08 UTCGHSA enrichment
  8. 2026-08-30 01:08 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  9. 2026-08-29 06:21 UTCNVD update
  10. 2026-08-29 06:13 UTCEG score recompute
  11. 2026-08-29 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16947?
CVE-2026-16947 is a critical vulnerability published on August 29, 2026. The Total processing card payments for WooCommerce WordPress plugin through 7.3 does not validate a user-supplied path before using it to build a server-side verification request, and does not verify the authenticity of the response, allowing unauthenticated attackers to redirect that request to an…
When was CVE-2026-16947 disclosed?
CVE-2026-16947 was first published in the National Vulnerability Database on August 29, 2026, with the most recent update on August 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16947 actively exploited?
CVE-2026-16947 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-16947?
CVE-2026-16947 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16947?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16947, 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-16947

Explore →

Is Your Infrastructure Affected by CVE-2026-16947?

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

Start Free Scan →Browse All CVEs