CVE-2026-103327: The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment noti
CVE-2026-103327 is a medium-severity flaw (CVSS 5.3) affecting affected software. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | n/a |
| CISA exploited list | No |
| Published | 2026-11-03 |
| Last modified | 2026-11-03 |
Last updated 2026-11-03 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Timeline
- Published CVE record published
- Updated Record last modified
Advisories and coverage
Research and news
- VulDB Recent Entries: CVE-2026-103327 | CryptoCloud Plugin up to 3.0.1 on WordPress Gateway Callback data authenticity 2026-11-03
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-103327?
No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.
Is CVE-2026-103327 being exploited?
CVE-2026-103327 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-103327 affect?
CVE-2026-103327 affects affected software. Severity is medium (CVSS 5.3). 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 defaul
How urgent is CVE-2026-103327?
Priority 24/100. Remotely exploitable, no login, no user action