Pay With MetaMask For WooCommerce – Cryptocurrency Payment Gateway <= 1.7.2 — Unauthenticated Arbitrary Order Payment Bypass
CVE-2026-107420Published · Updated Action summary
Affected: ≤1.7.2Update to 1.7.3 or newer
All remediation steps- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- 0.1% chance in 30 days2th percentile
- CISA KEV
- Not listed
On this page7
Am I affected?
Pay With MetaMask For WooCommerce – Cryptocurrency Payment Gateway cryptocurrency-payments-using-metamask-for-woocommerce
- Affected≤ 1.7.2
- Patched in1.7.3
Update to 1.7.3 or newer.
You are affected if you run ≤ 1.7.2. Version 1.7.3 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Pay With MetaMask For WooCommerce – Cryptocurrency Payment Gateway.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 1.7.3, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Pay With MetaMask For WooCommerce – Cryptocurrency Payment Gateway to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to luffy.
The Pay With MetaMask For WooCommerce – Cryptocurrency Payment Gateway plugin for WordPress is vulnerable to Bypass Vulnerability in all versions up to, and including, 1.7.2. This is due to the transaction verification function accepted a caller-supplied amount and read the receiver address from global plugin settings rather than from trusted order metadata, allowing the expected payment parameters to be manipulated by the client. This makes it possible for unauthenticated attackers to mark WooCommerce orders as paid without completing a valid on-chain payment matching the order's expected receiver, amount, and token contract.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Timeline
CVE published
Severity medium, CVSS 5.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- EPSS
- Exploit Prediction Scoring System by FIRST.org.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.
