PatchSiren cyber security CVE debrief
CVE-2026-96895 WP YouTube Lyte CVE debrief
The WP YouTube Lyte WordPress plugin before 1.7.31 does not escape some attributes of YouTube embed blocks before outputting them in an HTML attribute when rendering the block. This could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks. The vulnerability impacts WordPress installations using the WP YouTube Lyte plugin, particularly those with users having contributor roles. Defenders and administrators should assess exposure and prioritize updating the plugin to mitigate potential Stored Cross-Site Scripting attacks.
- Vendor
- WP YouTube Lyte
- Product
- WP YouTube Lyte WordPress plugin
- CVSS
- MEDIUM 6.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-27
- Original CVE updated
- 2026-09-28
- Advisory published
- 2026-09-27
- Advisory updated
- 2026-09-28
Who should care
Defenders and administrators of WordPress installations using the WP YouTube Lyte plugin, especially those with users having contributor roles, should assess exposure and prioritize updating the plugin.
Why it matters
The WP YouTube Lyte WordPress plugin vulnerability allows Stored Cross-Site Scripting attacks, impacting users with contributor roles, and requires verification and updates to mitigate.
- Potential for Stored Cross-Site Scripting attacks
- Exposure for users with contributor roles
- Need for verification and updates to the WP YouTube Lyte plugin
Technical summary
The WP YouTube Lyte WordPress plugin before 1.7.31 does not escape some attributes of YouTube embed blocks before outputting them in an HTML attribute when rendering the block, allowing users with a role as low as contributor to perform Stored Cross-Site Scripting attacks. The vulnerability is caused by insufficient input validation and sanitization of user-supplied data. Defenders should prioritize verifying and updating the WP YouTube Lyte WordPress plugin to version 1.7.31 or later, and assess exposure for users with contributor roles.
Defensive priority
Defenders should prioritize verifying and updating the WP YouTube Lyte WordPress plugin to version 1.7.31 or later, and assess exposure for users with contributor roles.
Recommended defensive actions
- Verify and update the WP YouTube Lyte WordPress plugin to version 1.7.31 or later
- Assess exposure for users with contributor roles
- Monitor for potential Stored Cross-Site Scripting attacks
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD vulnerability detail page provide information on the vulnerability, but limited details are available on exploitation or impact. The WPScan source reference also provides additional context on the vulnerability. Defenders should verify the vulnerability and update the WP YouTube Lyte WordPress plugin to version 1.7.31 or later. The vulnerability allows Stored Cross-Site Scripting attacks, impacting users with contributor roles.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-96895 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-96895
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-96895 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-96895
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/15978f11-a7bd-41f0-94bf-069be4d03987/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.