Quick answers
- Is CVE-2026-10530 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10530 being exploited in the wild.
- How severe is CVE-2026-10530?
- Informational severity, with a CVSS score of 5.3, published 22 June 2026.
- Which products and versions are affected?
- Pie Register < 3.8.4.10.
- Is there a fix for CVE-2026-10530?
- A patch was published on 2026-06-01: Fixed in version 3.8.4.10 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-10530 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-10530?
- Check whether you run Pie Register at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Pie Register plugin for WordPress fails to use a cryptographically secure pseudo-random number generator (CSPRNG) for account verification tokens in versions prior to 3.8.4.10. Specifically, the activation token was generated using an MD5 hash of the current Unix timestamp (time()). Because the server's time can be determined from HTTP response headers, an unauthenticated attacker can predict the valid token within a small window of candidates. By submitting these predicted hashes to the activation endpoint, an attacker can successfully activate a newly registered account without access to the associated email inbox. The issue is resolved in version 3.8.4.10 by switching to the wp_generate_password() function for token generation.
Affected products
- Pie Register Pie Register < 3.8.4.10
Timeline
- 2026-06-01: disclosed: Vulnerability details published by WPScan
- 2026-06-01: patched: Fixed in version 3.8.4.10
- 2026-06-22: advisory: CVE-2026-10530 published to NVD