The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment notifications received by its gateway callback, as the integrity check is skipped while the webhook secret is left at its empty default, allowing unauthenticated attackers to mark arbitrary orders as paid or failed without any payment being made.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 03 Nov 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress-extensions
Wordpress-extensions cryptocloud |
|
| Vendors & Products |
Wordpress-extensions
Wordpress-extensions cryptocloud |
Tue, 03 Nov 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-306 |
Tue, 03 Nov 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment notifications received by its gateway callback, as the integrity check is skipped while the webhook secret is left at its empty default, allowing unauthenticated attackers to mark arbitrary orders as paid or failed without any payment being made. | |
| Title | CryptoCloud - Crypto Payment Gateway 3.0.0 - 3.0.1 - Unauthenticated Arbitrary Order Payment Forgery via Empty-Default Webhook Secret | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-11-03T08:20:21.840Z
Reserved: 2026-09-30T12:35:33.368Z
Link: CVE-2026-103327
No data.
Status : Deferred
Published: 2026-11-03T09:17:08.647
Modified: 2026-11-03T16:30:49.290
Link: CVE-2026-103327
No data.
OpenCVE Enrichment
Updated: 2026-11-03T16:24:34Z
Weaknesses