Description
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.
Published: 2026-08-29
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in the Total Processing Card Payments for WooCommerce until version 7.3 fails to validate user supplied paths before constructing server‑side verification requests, and does not confirm the authenticity of the response. As a result, attackers can send unauthenticated requests that redirect the verification call to arbitrary hosts, exposing the merchant’s payment‑gateway credentials. They can also forge a success response that causes WooCommerce orders to be marked as paid without any real transaction. The likely attack vector is through unauthenticated HTTP requests to an exposed plugin endpoint, as the plugin accepts a path parameter from any visitor.

Affected Systems

The vulnerability affects the "Total processing card payments for WooCommerce" WordPress plugin for all versions up to and including 7.3. No sub‑vendor or alternative product names are listed in the available data.

Risk and Exploitability

Because the flaw can be triggered without authentication, an attacker only needs an HTTP client and knowledge of the vulnerable endpoint. The resulting information exposure (credential disclosure) can lead to compromise of the merchant’s payment gateway and theft of funds. Although a CVSS score is not provided and the EPSS value is unavailable, the potential financial impact and lack of authentication make the risk high. The instance is not currently listed in CISA’s Known Exploited Vulnerabilities catalog.

Generated by OpenCVE AI on August 29, 2026 at 07:56 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Total Processing Card Payments for WooCommerce plugin to a version newer than 7.3 if available.
  • Restrict access to the plugin’s payment verification endpoint so that only authenticated administrators can invoke it, for example by adding .htaccess rules or firewall restrictions.
  • Immediately rotate any payment‑gateway credentials that may have been exposed and audit recent orders for unauthorized completion.

Generated by OpenCVE AI on August 29, 2026 at 07:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 29 Aug 2026 08:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-918

Sat, 29 Aug 2026 06:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Total Processing Card Payments for WooCommerce <= 7.3 - Unauthenticated SSRF leading to Payment Bypass and Gateway Credential Disclosure
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-29T06:00:19.359Z

Reserved: 2026-07-24T08:01:59.597Z

Link: CVE-2026-16947

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-29T06:17:05.583

Modified: 2026-08-29T06:17:05.583

Link: CVE-2026-16947

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-29T08:00:05Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-918

    Server-Side Request Forgery (SSRF)