Total processing card payments for WooCommerce <= 7.3 - Unauthenticated Server-Side Request Forgery
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Total processing card payments for WooCommerce
- Affected Version
<= 7.3- CVSS
- 7.2High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-16947
At a glance
CVE-2026-16947 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Total processing card payments for WooCommerce WordPress plugin, affecting versions <= 7.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Pablo González Pérez.
Vulnerability Overview
The Total processing card payments for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 7.3. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Total processing card payments for WooCommerce <= 7.3 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this plugin is recorded for Total processing card payments for WooCommerce yet, so installs running <= 7.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Total processing card payments for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C