Security readout for executives and security teams
Plain-English summary
A flaw in the Total Processing Card Payments for WooCommerce plugin can let an unauthenticated attacker make unpaid orders appear paid and expose merchant payment-gateway credentials. A successful attack could cause direct revenue loss, fraudulent fulfillment, and credential compromise without requiring a WordPress account.
Executive priority
Treat this as an immediate payment-integrity incident risk. Within hours, establish exposure, independently reconcile recent paid orders, and protect gateway credentials. If the affected plugin is active and no verified fix is available, evaluate suspending that payment method while maintaining a safe alternative checkout path.
Technical view
Through version 7.3, the plugin uses an unvalidated user-controlled path to construct a server-side verification request and does not authenticate the returned response. This enables server-side request forgery, credential disclosure to an arbitrary host, and forged payment-success responses. CVSS 3.1 is 9.1: network-accessible, low complexity, no privileges, and no user interaction.
Likely exposure
Internet-accessible WooCommerce sites using this payment plugin through version 7.3 are potentially exposed. The bundle does not identify affected configuration requirements, deployment prevalence, or a confirmed fixed version. Sites not using the plugin are not implicated by the supplied evidence.
Exploitation context
The source bundle labels the WPScan reference as exploit-related, but provides no evidence of observed in-the-wild exploitation. The CVE is not listed as KEV in the bundle. Exploitation status should therefore be treated as unconfirmed, despite the low-complexity, unauthenticated attack conditions.
Researcher notes
CWE-918 explains the SSRF component, but the larger business impact comes from combining request redirection with unauthenticated response trust. The supplied sources do not establish a fixed version, vendor identity, affected endpoint, exploitation telemetry, or configuration prerequisites. Avoid interpreting the WPScan exploit tag as proof of active attacks.
Mitigation direction
- Identify and prioritize every site running the plugin through version 7.3.
- Check current vendor and WPScan guidance for a fixed release or supported mitigation.
- Consider disabling the affected payment integration until authoritative remediation guidance is available.
- Rotate payment-gateway credentials if investigation indicates disclosure or suspicious verification traffic.
- Delay fulfillment of suspicious orders until payment is independently confirmed with the processor.
Validation and detection
- Inventory WordPress installations and confirm the installed plugin version and activation status.
- Reconcile WooCommerce paid orders against payment-processor authorization and settlement records.
- Review recent orders for unexpected payment-state changes, fraud indicators, or fulfillment without processor confirmation.
- Inspect server, proxy, and egress logs for verification requests reaching unexpected destinations.
- Review gateway activity for credential use from unfamiliar systems or locations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-16947 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/53fe46b3-e8c4-448e-aa80-b7fb02fffa51/CVE reference, WPScan · exploit, vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE mapping pending import
This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.