CVE-2025-13849: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in matiasanca Cool YT Player
CVE-2025-13849 is a stored Cross-Site Scripting (XSS) vulnerability in the Cool YT Player WordPress plugin, affecting all versions up to 1. 0. Authenticated users with Contributor-level access or higher can exploit insufficient input sanitization on the 'videoid' parameter to inject malicious scripts. These scripts execute whenever any user visits the compromised page, potentially leading to session hijacking, privilege escalation, or defacement. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction but does require authentication with limited privileges. No known public exploits exist yet, but the vulnerability poses a risk to websites using this plugin. European organizations using Cool YT Player should prioritize patching or mitigating this issue to prevent exploitation. Countries with high WordPress usage and significant web publishing sectors are most likely to be affected.
AI Analysis
Technical Summary
CVE-2025-13849 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Cool YT Player plugin for WordPress, maintained by matiasanca. The vulnerability arises from improper neutralization of input during web page generation, specifically through the 'videoid' parameter. All versions up to and including 1.0 are affected due to insufficient input sanitization and output escaping, allowing authenticated users with Contributor-level permissions or higher to inject arbitrary JavaScript code. This malicious code is stored persistently and executed in the context of any user who accesses the infected page, potentially compromising session tokens, cookies, or enabling further attacks such as privilege escalation or defacement. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with an attack vector of network (remote), low attack complexity, requiring privileges (Contributor or above), no user interaction, and a scope change. Although no public exploits are currently known, the vulnerability's presence in a popular WordPress plugin increases the risk of exploitation, especially in environments where multiple users have contributor or higher roles. The stored XSS nature means the impact can be widespread across site visitors and administrators. The lack of available patches at the time of publication necessitates immediate mitigation efforts by affected organizations.
Potential Impact
For European organizations, the impact of this vulnerability can be significant, particularly for those relying on WordPress sites with multiple contributors or editors. Exploitation could lead to session hijacking, allowing attackers to impersonate legitimate users, including administrators, potentially leading to full site compromise. Data integrity may be affected through unauthorized content modification or defacement. Confidential information accessible via the web interface could be exposed or manipulated. The vulnerability does not affect availability directly but can indirectly cause service disruption through malicious script execution or administrative lockout. Organizations in sectors such as media, e-commerce, education, and government that maintain WordPress-based websites are at heightened risk. Additionally, the stored XSS can facilitate further attacks like phishing or malware distribution to site visitors, amplifying reputational damage and compliance risks under regulations like GDPR.
Mitigation Recommendations
Given the absence of an official patch, European organizations should implement immediate compensating controls. First, restrict Contributor-level access strictly to trusted users and review existing user roles to minimize privilege exposure. Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'videoid' parameter. Conduct thorough input validation and sanitization on the server side if custom development is possible. Monitor logs and website content for suspicious script injections or unexpected changes. Educate content contributors about the risks of injecting untrusted content. Consider temporarily disabling or replacing the Cool YT Player plugin with alternative, secure video players until a patch is released. Regularly update WordPress core and other plugins to reduce the attack surface. Finally, prepare incident response plans to quickly address any exploitation attempts.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden, Belgium, Austria
CVE-2025-13849: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in matiasanca Cool YT Player
Description
CVE-2025-13849 is a stored Cross-Site Scripting (XSS) vulnerability in the Cool YT Player WordPress plugin, affecting all versions up to 1. 0. Authenticated users with Contributor-level access or higher can exploit insufficient input sanitization on the 'videoid' parameter to inject malicious scripts. These scripts execute whenever any user visits the compromised page, potentially leading to session hijacking, privilege escalation, or defacement. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction but does require authentication with limited privileges. No known public exploits exist yet, but the vulnerability poses a risk to websites using this plugin. European organizations using Cool YT Player should prioritize patching or mitigating this issue to prevent exploitation. Countries with high WordPress usage and significant web publishing sectors are most likely to be affected.
AI-Powered Analysis
Technical Analysis
CVE-2025-13849 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Cool YT Player plugin for WordPress, maintained by matiasanca. The vulnerability arises from improper neutralization of input during web page generation, specifically through the 'videoid' parameter. All versions up to and including 1.0 are affected due to insufficient input sanitization and output escaping, allowing authenticated users with Contributor-level permissions or higher to inject arbitrary JavaScript code. This malicious code is stored persistently and executed in the context of any user who accesses the infected page, potentially compromising session tokens, cookies, or enabling further attacks such as privilege escalation or defacement. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with an attack vector of network (remote), low attack complexity, requiring privileges (Contributor or above), no user interaction, and a scope change. Although no public exploits are currently known, the vulnerability's presence in a popular WordPress plugin increases the risk of exploitation, especially in environments where multiple users have contributor or higher roles. The stored XSS nature means the impact can be widespread across site visitors and administrators. The lack of available patches at the time of publication necessitates immediate mitigation efforts by affected organizations.
Potential Impact
For European organizations, the impact of this vulnerability can be significant, particularly for those relying on WordPress sites with multiple contributors or editors. Exploitation could lead to session hijacking, allowing attackers to impersonate legitimate users, including administrators, potentially leading to full site compromise. Data integrity may be affected through unauthorized content modification or defacement. Confidential information accessible via the web interface could be exposed or manipulated. The vulnerability does not affect availability directly but can indirectly cause service disruption through malicious script execution or administrative lockout. Organizations in sectors such as media, e-commerce, education, and government that maintain WordPress-based websites are at heightened risk. Additionally, the stored XSS can facilitate further attacks like phishing or malware distribution to site visitors, amplifying reputational damage and compliance risks under regulations like GDPR.
Mitigation Recommendations
Given the absence of an official patch, European organizations should implement immediate compensating controls. First, restrict Contributor-level access strictly to trusted users and review existing user roles to minimize privilege exposure. Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'videoid' parameter. Conduct thorough input validation and sanitization on the server side if custom development is possible. Monitor logs and website content for suspicious script injections or unexpected changes. Educate content contributors about the risks of injecting untrusted content. Consider temporarily disabling or replacing the Cool YT Player plugin with alternative, secure video players until a patch is released. Regularly update WordPress core and other plugins to reduce the attack surface. Finally, prepare incident response plans to quickly address any exploitation attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-12-01T19:48:20.990Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 695e4c117349d0379d7d568c
Added to database: 1/7/2026, 12:05:37 PM
Last enriched: 1/14/2026, 3:54:40 PM
Last updated: 2/7/2026, 2:26:32 AM
Views: 17
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-2071: Buffer Overflow in UTT 进取 520W
HighCVE-2026-25762: CWE-400: Uncontrolled Resource Consumption in adonisjs core
HighCVE-2026-25754: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in adonisjs core
HighCVE-2026-25644: CWE-295: Improper Certificate Validation in datahub-project datahub
HighCVE-2026-25804: CWE-287: Improper Authentication in antrea-io antrea
HighActions
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.