CVE-2026-10530
Received Received - Intake
Account Activation Token Prediction in Pie Register WordPress Plugin

Publication date: 2026-06-22

Last updated on: 2026-06-22

Assigner: WPScan

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-22
Last Modified
2026-06-22
Generated
2026-06-22
AI Q&A
2026-06-22
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
pie_register pie_register to 3.8.4.10 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The Pie Register WordPress plugin before version 3.8.4.10 has a vulnerability where it generates account verification tokens using predictable values based on the server's timestamp (md5(time())).

Because these tokens are not sufficiently random, unauthenticated attackers can predict valid tokens within a small time window.

This allows attackers to activate user accounts without having access to the associated email inbox, effectively bypassing the email verification process.

Impact Analysis

This vulnerability can allow attackers to activate accounts without verifying ownership of the associated email address.

As a result, unauthorized users could gain access to accounts or services that require email verification, potentially leading to unauthorized access or abuse of the system.

It undermines the authentication process and could facilitate further attacks or misuse of the affected WordPress site.

Detection Guidance

This vulnerability can be detected by attempting to predict account activation tokens generated by the Pie Register plugin prior to version 3.8.4.10. Since the tokens are generated using md5(time()), an attacker can capture the server time, compute possible tokens within a small time window, and test these tokens against the activation endpoint to see if any are valid.

A practical approach involves monitoring HTTP requests to the activation endpoint and checking for token patterns that match md5 hashes of recent timestamps.

Suggested commands might include using curl or wget to test token values against the activation URL, for example:

  • Use a script to generate md5 hashes of timestamps around the current time.
  • Use curl to send requests to the activation endpoint with these tokens, e.g., curl "https://example.com/activate?token=<generated_token>"
  • Analyze server logs for repeated activation attempts with predictable tokens.
Mitigation Strategies

The immediate step to mitigate this vulnerability is to update the Pie Register WordPress plugin to version 3.8.4.10 or later, where the token generation method was fixed to use a stronger and more secure function (wp_generate_password(32, false)) instead of predictable md5(time()).

Until the update can be applied, consider monitoring and restricting access to the account activation endpoint to prevent unauthorized token guessing.

Additionally, review and enhance logging and alerting for suspicious activation attempts.

Compliance Impact

This vulnerability allows unauthenticated attackers to bypass email verification by predicting account activation tokens, enabling account activation without access to the associated email inbox.

Such unauthorized account activation could lead to unauthorized access to user accounts and potentially sensitive personal data.

This situation may impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal data and secure authentication mechanisms to prevent unauthorized access.

Specifically, the vulnerability relates to broken authentication and insufficient cryptography, which are critical controls in these regulations to ensure data confidentiality and integrity.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-10530. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart