CVE-2026-16947
Unauthenticated flaw allows forging order payments and exfiltrating gateway creds.
Is CVE-2026-16947 being exploited?
Not confirmed. CVE-2026-16947 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-16947?
CVE-2026-16947 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-16947?
Not known from our data. No patch reference has been recorded for CVE-2026-16947, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-16947 affect?
CVE-2026-16947 affects Total Processing for WooCommerce plugin (<=7.3), WordPress sites running WooCommerce, Merchant payment gateways (credentials exposure). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16947?
Apply vendor patch or disable plugin; block outbound verification hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can redirect server verification to attacker-controlled hosts to exfiltrate merchant payment-gateway credentials and forge responses to mark orders as paid.
Immediate action required
- affected<= 7.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.