Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-96895 Overview
CVE-2026-96895 is a stored Cross-Site Scripting (XSS) vulnerability in the WP YouTube Lyte WordPress plugin versions prior to 1.7.31. The plugin fails to escape certain attributes of YouTube embed blocks before outputting them inside HTML attributes during block rendering. Authenticated users with a role as low as contributor can inject malicious JavaScript that executes in the browser of any visitor viewing the affected post. The weakness is classified under CWE-79: Improper Neutralization of Input During Web Page Generation.
Critical Impact
Authenticated contributors can store malicious JavaScript in YouTube embed blocks, enabling session hijacking, administrative account takeover, and arbitrary actions in the context of victims who view compromised content.
Affected Products
- WP YouTube Lyte WordPress plugin versions before 1.7.31
- WordPress sites allowing contributor-level accounts or higher to publish content using the plugin
- Any WordPress installation rendering YouTube embed blocks via the vulnerable plugin
Discovery Timeline
- 2026-09-27 - CVE-2026-96895 published to the National Vulnerability Database
- 2026-09-28 - Record last modified in NVD
Technical Details for CVE-2026-96895
Vulnerability Analysis
The vulnerability resides in the block rendering path of the WP YouTube Lyte plugin. When the plugin processes a YouTube embed block, it reads attribute values supplied by the post author and emits them into HTML attributes without applying proper escaping. Because the output is placed within an attribute context, standard HTML entity escaping for angle brackets is insufficient; characters such as double quotes and single quotes must also be neutralized. The absence of attribute-safe escaping lets a contributor break out of the attribute value and inject new attributes, including event handlers that execute JavaScript when a visitor loads the page.
Contributors in WordPress can author posts but normally cannot publish them without editorial review. Stored XSS of this type weaponizes the review workflow itself: once an editor or administrator previews the post, the payload executes with their session, potentially leading to administrative compromise.
Root Cause
The root cause is missing output escaping in the block render callback. The plugin trusts attribute values from the block editor and concatenates them into the rendered HTML. Proper mitigation requires applying esc_attr() (or an equivalent attribute-context escaping function) to every dynamic value emitted into an HTML attribute.
Attack Vector
Exploitation requires an authenticated account with at least contributor privileges and user interaction from a higher-privileged user who views the post. The attacker inserts a YouTube embed block and tampers with the block attributes to include an XSS payload. When the post is previewed or published, the unescaped attribute is rendered into the page and the payload executes in the viewer's browser session. No code example is published; see the WPScan Vulnerability Advisory for technical specifics.
Detection Methods for CVE-2026-96895
Indicators of Compromise
- Post revisions containing YouTube embed block attributes with suspicious characters such as ", onerror=, onload=, or javascript: sequences
- Unexpected <script> tags or inline event handlers rendered inside pages that embed YouTube videos
- Outbound browser requests from administrator sessions to attacker-controlled domains shortly after viewing posts authored by contributors
Detection Strategies
- Audit the wp_posts and wp_postmeta tables for block markup referencing WP YouTube Lyte with attribute values containing HTML metacharacters
- Review contributor-authored drafts prior to editorial preview, specifically inspecting embed block attributes
- Monitor WordPress audit logs for new contributor accounts creating or editing posts that contain YouTube embeds
Monitoring Recommendations
- Enable WordPress activity logging to track post edits, user role changes, and plugin configuration changes
- Deploy a Content Security Policy (CSP) that restricts inline script execution to surface injection attempts in browser reports
- Alert on administrator accounts loading post previews that originate from contributor roles
How to Mitigate CVE-2026-96895
Immediate Actions Required
- Update the WP YouTube Lyte plugin to version 1.7.31 or later on all WordPress installations
- Review existing posts containing YouTube embed blocks for malicious attribute content and purge affected revisions
- Rotate credentials and session tokens for administrator and editor accounts that previewed contributor content before patching
Patch Information
The maintainer addressed the issue in WP YouTube Lyte version 1.7.31 by applying proper escaping to YouTube embed block attributes before output. Refer to the WPScan Vulnerability Advisory for coordinated advisory details and version guidance.
Workarounds
- Temporarily restrict contributor and author roles from using the YouTube embed block until the plugin is updated
- Disable the WP YouTube Lyte plugin on sites where patching cannot be performed immediately
- Require editorial review in an isolated browser profile that is not authenticated to the WordPress admin panel
# Update WP YouTube Lyte via WP-CLI
wp plugin update wp-youtube-lyte --version=1.7.31
# Verify installed version
wp plugin get wp-youtube-lyte --field=version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

