CVE-2025-6692: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in hanucodes YouTube Embed – YouTube Gallery, Vimeo Gallery – WordPress Plugin
The YouTube Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘instance’ parameter in all versions up to, and including, 10.3 due to insufficient input sanitization and output escaping. 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-2025-6692 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, found in the YouTube Embed – YouTube Gallery, Vimeo Gallery WordPress plugin developed by hanucodes. This vulnerability affects all versions up to and including 10.3. The root cause is insufficient sanitization and escaping of the 'instance' parameter during web page generation, which allows authenticated users with Contributor-level access or higher to inject arbitrary JavaScript code into pages. Because the injected scripts are stored persistently, they execute every time a user accesses the affected page, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of users. The vulnerability requires no user interaction beyond visiting the infected page but does require the attacker to have at least Contributor privileges, which are commonly granted to trusted users who can create or edit content. The CVSS 3.1 base score is 6.4 (medium severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and partial confidentiality and integrity impacts. No public exploits have been reported yet, but the vulnerability poses a significant risk due to the widespread use of WordPress and this plugin. The lack of a patch at the time of reporting necessitates immediate mitigation steps to reduce exposure.
Potential Impact
The impact of CVE-2025-6692 is primarily on the confidentiality and integrity of affected WordPress sites and their users. Attackers with Contributor-level access can inject malicious scripts that execute in the context of other users' browsers, potentially leading to session hijacking, credential theft, unauthorized content modification, or distribution of malware. This can erode user trust, damage brand reputation, and lead to regulatory compliance issues if sensitive user data is compromised. Since the vulnerability does not affect availability directly, denial-of-service is less likely. However, the scope is broad because WordPress powers a significant portion of the web, and the affected plugin is popular for embedding video galleries. Organizations relying on this plugin, especially those with multiple contributors, face increased risk of insider threats or compromised contributor accounts being leveraged to exploit this vulnerability. The medium severity score suggests a moderate but actionable risk that should be addressed promptly to avoid escalation.
Mitigation Recommendations
To mitigate CVE-2025-6692, organizations should: 1) Monitor for and apply security patches or updates from hanucodes as soon as they become available. 2) Temporarily restrict Contributor-level permissions to trusted users only or reduce the number of users with such privileges to limit potential attackers. 3) Implement additional input validation and output encoding at the application or web server level to sanitize the 'instance' parameter and other user inputs. 4) Employ Web Application Firewalls (WAFs) with rules targeting XSS payloads to detect and block malicious requests. 5) Conduct regular security audits of user-generated content and plugin configurations to identify suspicious scripts or behavior. 6) Educate content contributors about security best practices and the risks of injecting untrusted content. 7) Consider alternative plugins with better security track records if immediate patching is not feasible. These steps collectively reduce the attack surface and limit the potential for exploitation until a permanent fix is deployed.
Affected Countries
United States, India, Brazil, Germany, United Kingdom, Canada, Australia, France, Japan, Netherlands, Italy, Spain
CVE-2025-6692: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in hanucodes YouTube Embed – YouTube Gallery, Vimeo Gallery – WordPress Plugin
Description
The YouTube Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘instance’ parameter in all versions up to, and including, 10.3 due to insufficient input sanitization and output escaping. 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
Machine-generated threat intelligence
Technical Analysis
CVE-2025-6692 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, found in the YouTube Embed – YouTube Gallery, Vimeo Gallery WordPress plugin developed by hanucodes. This vulnerability affects all versions up to and including 10.3. The root cause is insufficient sanitization and escaping of the 'instance' parameter during web page generation, which allows authenticated users with Contributor-level access or higher to inject arbitrary JavaScript code into pages. Because the injected scripts are stored persistently, they execute every time a user accesses the affected page, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of users. The vulnerability requires no user interaction beyond visiting the infected page but does require the attacker to have at least Contributor privileges, which are commonly granted to trusted users who can create or edit content. The CVSS 3.1 base score is 6.4 (medium severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and partial confidentiality and integrity impacts. No public exploits have been reported yet, but the vulnerability poses a significant risk due to the widespread use of WordPress and this plugin. The lack of a patch at the time of reporting necessitates immediate mitigation steps to reduce exposure.
Potential Impact
The impact of CVE-2025-6692 is primarily on the confidentiality and integrity of affected WordPress sites and their users. Attackers with Contributor-level access can inject malicious scripts that execute in the context of other users' browsers, potentially leading to session hijacking, credential theft, unauthorized content modification, or distribution of malware. This can erode user trust, damage brand reputation, and lead to regulatory compliance issues if sensitive user data is compromised. Since the vulnerability does not affect availability directly, denial-of-service is less likely. However, the scope is broad because WordPress powers a significant portion of the web, and the affected plugin is popular for embedding video galleries. Organizations relying on this plugin, especially those with multiple contributors, face increased risk of insider threats or compromised contributor accounts being leveraged to exploit this vulnerability. The medium severity score suggests a moderate but actionable risk that should be addressed promptly to avoid escalation.
Mitigation Recommendations
To mitigate CVE-2025-6692, organizations should: 1) Monitor for and apply security patches or updates from hanucodes as soon as they become available. 2) Temporarily restrict Contributor-level permissions to trusted users only or reduce the number of users with such privileges to limit potential attackers. 3) Implement additional input validation and output encoding at the application or web server level to sanitize the 'instance' parameter and other user inputs. 4) Employ Web Application Firewalls (WAFs) with rules targeting XSS payloads to detect and block malicious requests. 5) Conduct regular security audits of user-generated content and plugin configurations to identify suspicious scripts or behavior. 6) Educate content contributors about security best practices and the risks of injecting untrusted content. 7) Consider alternative plugins with better security track records if immediate patching is not feasible. These steps collectively reduce the attack surface and limit the potential for exploitation until a permanent fix is deployed.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-06-25T22:45:19.150Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68889537ad5a09ad008cc7dc
Added to database: 7/29/2025, 9:32:39 AM
Last enriched: 2/26/2026, 3:44:45 PM
Last updated: 3/23/2026, 11:55:46 PM
Views: 105
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.