Pie Register: A security weakness
Pie Register is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 3.8.4.10.
- Component
- Pie Register
- Plugin slug
pie-register- Affected
- < 3.8.4.10
- Safe version
3.8.4.10- Published
- Jun 22, 2026
- Weakness
- Not assigned
This CVE was published Jun 22, 2026 and is one of 18 known issues for this plugin.
Update, patch or deactivate.
Update Pie Register to 3.8.4.10 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Pie Register WordPress plugin before 3.8.4.10 does not use sufficiently random values when generating its account verification tokens, allowing unauthenticated attackers to predict a valid token and activate an account without access to the associated email inbox.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N