Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-16947 – Unauthenticated SSRF / Payment Fraud – Total Processing Card Payments for WooCommer

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-16947 is a critical unauthenticated Server-Side Request Forgery (SSRF, CWE-918) vulnerability in the "Total processing card payments for WooCommerce" WordPress plugin, affecting all versions up to and including 7.3. The plugin fails to validate a user-supplied path before using it to build a server-side payment-verification request and does not authenticate the response it receives, letting a remote unauthenticated attacker redirect that request to an arbitrary host. The flaw carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: the plugin builds a server-side verification request using a user-controllable path/parameter without validating that it points to the legitimate payment gateway, and does not verify the authenticity of the response returned.
  • Trigger conditions: an attacker sends a crafted request to the WooCommerce checkout/verification endpoint exposed by the plugin, supplying an attacker-controlled destination instead of the expected payment gateway host.
  • Attack vector: network, no authentication and no user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: the SSRF can be used to redirect outbound verification requests to an attacker-controlled server, exposing merchant payment-gateway credentials sent in that request, and to return a forged "success" response that marks arbitrary WooCommerce orders as paid without any real payment being made — enabling payment fraud alongside credential disclosure.

Affected software

  • Total processing card payments for WooCommerce (WordPress plugin) — all versions through 7.3

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: no patched version has been published for this plugin at time of writing; sites running "Total processing card payments for WooCommerce" ≤ 7.3 should check for a newer release and update as soon as one becomes available.
  • If no patch is available: disable or deactivate the plugin until a fix is released; restrict or firewall outbound requests originating from the plugin’s verification endpoint so they cannot be redirected to arbitrary hosts; monitor WooCommerce orders for unexpected transitions to "paid"/"completed" status without a corresponding real transaction; rotate payment-gateway API credentials if compromise is suspected.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: /wp-content/plugins/totalprocessing-card-payments/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge