ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-16947

Server-Side Request Forgery (SSRF)

Published Aug 29, 2026 · catalog updated Oct 22, 2026 · Total Processing Total Processing Card Payments for WooCommerce

Patch now

CVE-2026-16947 is in the CISA known-exploited catalog. Confirm Total Processing Total Processing Card Payments for WooCommerce against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Severity
Critical9.1
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
0.24%
Remediation
Remediation guidance
Affected products
stated Total processing card payments for WooCommerce · vendor Total Processing Total Processing Card Payments for WooCommerce · vendor Unknown Total processing card payments for WooCommerce

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated Total processing card payments for WooCommerce<= 7.3
  • vendor Total Processing Total Processing Card Payments for WooCommerceversion unspecified
  • vendor Unknown Total processing card payments for WooCommerceversion unspecified

How to fix CVE-2026-16947

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2026-16947 is in the CISA known-exploited catalog. Confirm Total Processing Total Processing Card Payments for WooCommerce against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Compare what you have installed with Total processing card payments for WooCommerce <= 7.3. Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

What should an analyst verify?

No weakness class is stored. EPSS 0.24%. The CISA KEV listing is the exploitation evidence. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 22, 2026 · VulnCheck KEV

    Detected

    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 respon

  2. Oct 22, 2026 · CISA KEV

    Known exploited

    Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Sources

  • CVE.orgVulnerability recordCVE-2026-16947

    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

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-16947

    30-day exploitation probability 0.24%

    first.org
  • VulnCheck KEVConfirmed exploitationCVE-2026-16947

    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

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.