CVE-2026-1915: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in bestony Simple Plyr
The Simple Plyr plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'poster' parameter in the 'plyr' shortcode in all versions up to, and including, 0.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
AI Analysis
Technical Summary
CVE-2026-1915 is a stored Cross-Site Scripting vulnerability identified in the Simple Plyr plugin for WordPress, developed by bestony. The vulnerability exists in all versions up to and including 0.0.1 due to insufficient sanitization and escaping of the 'poster' parameter within the 'plyr' shortcode. This parameter accepts user input that is directly embedded into web pages without proper neutralization, enabling attackers with Contributor-level or higher privileges to inject arbitrary JavaScript code. Since the injected scripts are stored persistently, they execute every time a user accesses the affected page, potentially compromising user sessions, stealing credentials, or performing unauthorized actions on behalf of users. The vulnerability requires authenticated access but no user interaction, making it a significant risk within environments where multiple users have content editing rights. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, and partial impact on confidentiality and integrity. No patches or known exploits are currently available, indicating the need for immediate attention from site administrators. The vulnerability falls under CWE-79, highlighting improper input neutralization during web page generation as the root cause.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily to websites using the Simple Plyr plugin on WordPress platforms. Exploitation could lead to unauthorized script execution, resulting in session hijacking, data theft, or defacement of web content. This can damage organizational reputation, lead to data breaches involving user information, and potentially facilitate further attacks such as privilege escalation or lateral movement within internal networks. Given that the exploit requires authenticated access at Contributor level or above, organizations with multiple content editors or contributors are at higher risk. The impact is especially critical for sectors relying heavily on web presence and user trust, such as e-commerce, media, and public services. Additionally, the cross-site scripting vulnerability could be leveraged to bypass security controls or inject malicious payloads that affect visitors or administrators, increasing the attack surface. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation.
Mitigation Recommendations
Organizations should immediately audit their WordPress installations to identify the presence of the Simple Plyr plugin and verify the version in use. Since no official patches are currently available, administrators should consider temporarily disabling the plugin or restricting Contributor-level access until a fix is released. Implementing strict input validation and output encoding on the 'poster' parameter can mitigate the risk; this may involve custom code or web application firewall (WAF) rules to detect and block malicious payloads targeting this parameter. Additionally, monitoring logs for unusual activity related to shortcode usage or unexpected script injections can help detect exploitation attempts early. Educating content contributors about safe input practices and limiting the number of users with editing privileges reduces the attack surface. Finally, organizations should subscribe to security advisories from WordPress and bestony to apply patches promptly once available.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain
CVE-2026-1915: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in bestony Simple Plyr
Description
The Simple Plyr plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'poster' parameter in the 'plyr' shortcode in all versions up to, and including, 0.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
AI-Powered Analysis
Technical Analysis
CVE-2026-1915 is a stored Cross-Site Scripting vulnerability identified in the Simple Plyr plugin for WordPress, developed by bestony. The vulnerability exists in all versions up to and including 0.0.1 due to insufficient sanitization and escaping of the 'poster' parameter within the 'plyr' shortcode. This parameter accepts user input that is directly embedded into web pages without proper neutralization, enabling attackers with Contributor-level or higher privileges to inject arbitrary JavaScript code. Since the injected scripts are stored persistently, they execute every time a user accesses the affected page, potentially compromising user sessions, stealing credentials, or performing unauthorized actions on behalf of users. The vulnerability requires authenticated access but no user interaction, making it a significant risk within environments where multiple users have content editing rights. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, and partial impact on confidentiality and integrity. No patches or known exploits are currently available, indicating the need for immediate attention from site administrators. The vulnerability falls under CWE-79, highlighting improper input neutralization during web page generation as the root cause.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily to websites using the Simple Plyr plugin on WordPress platforms. Exploitation could lead to unauthorized script execution, resulting in session hijacking, data theft, or defacement of web content. This can damage organizational reputation, lead to data breaches involving user information, and potentially facilitate further attacks such as privilege escalation or lateral movement within internal networks. Given that the exploit requires authenticated access at Contributor level or above, organizations with multiple content editors or contributors are at higher risk. The impact is especially critical for sectors relying heavily on web presence and user trust, such as e-commerce, media, and public services. Additionally, the cross-site scripting vulnerability could be leveraged to bypass security controls or inject malicious payloads that affect visitors or administrators, increasing the attack surface. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation.
Mitigation Recommendations
Organizations should immediately audit their WordPress installations to identify the presence of the Simple Plyr plugin and verify the version in use. Since no official patches are currently available, administrators should consider temporarily disabling the plugin or restricting Contributor-level access until a fix is released. Implementing strict input validation and output encoding on the 'poster' parameter can mitigate the risk; this may involve custom code or web application firewall (WAF) rules to detect and block malicious payloads targeting this parameter. Additionally, monitoring logs for unusual activity related to shortcode usage or unexpected script injections can help detect exploitation attempts early. Educating content contributors about safe input practices and limiting the number of users with editing privileges reduces the attack surface. Finally, organizations should subscribe to security advisories from WordPress and bestony to apply patches promptly once available.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-04T15:40:10.946Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69901aedc9e1ff5ad86893d5
Added to database: 2/14/2026, 6:49:17 AM
Last enriched: 2/14/2026, 7:05:35 AM
Last updated: 2/21/2026, 12:20:28 AM
Views: 26
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.