CryptoCloud – Crypto Payment Gateway 3.0.0 — 3.0.1 - Unauthenticated Arbitrary Order Status Manipulation
CVE-2026-103327Published · Updated Action summary
Affected: 3.0.0 – 3.0.1No patch available
What to do until a fix ships- 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 days1th percentile
- CISA KEV
- Not listed
On this page8
Am I affected?
CryptoCloud – Crypto Payment Gateway cryptocloud-crypto-payment-gateway
- Affected3.0.0 – 3.0.1
- PatchedNo fix yet
No patched version available.
You are affected if you run 3.0.0 – 3.0.1. No fixed version has been released.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under CryptoCloud – Crypto 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
- 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.
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch CryptoCloud – Crypto Payment Gateway to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Naoki Kawahigashi.
The CryptoCloud – Crypto Payment Gateway plugin for WordPress is vulnerable to Missing Authentication in versions 3.0.0 through 3.0.1. This is due to a skipped integrity check on incoming payment gateway webhook notifications combined with a webhook secret that defaults to an empty value, meaning no signature validation is ever enforced. This makes it possible for unauthenticated attackers to mark arbitrary WooCommerce orders as paid or failed without completing any actual payment transaction.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in CryptoCloud – Crypto Payment Gateway
All 2| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Crypto Payment Gateway <= 2.1.2 - Missing Authorization ≤2.1.2Update to 2.3.2 | CVE-2025-48147 |
- Medium5.3Crypto Payment Gateway <= 2.1.2 - Missing Authorization
≤2.1.2Update to 2.3.2
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.
