CVE-2026-103327: CryptoCloud (WordPress plugin) · Insufficient Verification of Data Authenticity
Affects CryptoCloud (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 3 Nov 2026, 08:59 UTC
Thin evidence
One scorer or none| CNA (WPScan) | CVSS 3.1 | 5.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CryptoCloud | Affected
| Fixed in– |
AI-suggested
Users should ensure that the webhook secret is properly configured to a non-empty value to enforce integrity checks. Monitor the vendor's advisory for updates and apply any official fixes once available. Until then, avoid using affected versions or disable the payment notification feature if possible.
Description
The CryptoCloud WordPress plugin versions 3.0.0 through 3.0.1 have a vulnerability where payment notifications are not properly authenticated. This occurs because the webhook secret remains at its empty default, causing the plugin to skip integrity checks. As a result, unauthenticated attackers can mark orders as paid or failed without actual payment.