Skip to main content

CVE-2025-7809: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in streamweasels StreamWeasels Twitch Integration

Medium
VulnerabilityCVE-2025-7809cvecve-2025-7809cwe-79
Published: Tue Jul 29 2025 (07/29/2025, 03:41:21 UTC)
Source: CVE Database V5
Vendor/Project: streamweasels
Product: StreamWeasels Twitch Integration

Description

The StreamWeasels Twitch Integration plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'data-uuid' attribute in all versions up to, and including, 1.9.3 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

AILast updated: 07/29/2025, 04:33:01 UTC

Technical Analysis

CVE-2025-7809 is a Stored Cross-Site Scripting (XSS) vulnerability affecting the StreamWeasels Twitch Integration plugin for WordPress, specifically in all versions up to and including 1.9.3. The vulnerability arises from improper neutralization of user-supplied input in the 'data-uuid' attribute, where insufficient input sanitization and output escaping allow authenticated users with contributor-level access or higher to inject arbitrary JavaScript code. This malicious script is then stored and executed whenever any user accesses the affected page, potentially compromising user sessions, stealing cookies, or performing actions on behalf of users without their consent. The vulnerability has a CVSS 3.1 base score of 6.4, indicating a medium severity level. The attack vector is network-based with low attack complexity, requiring privileges equivalent to contributor-level access but no user interaction is needed for exploitation. The scope is changed, meaning the vulnerability affects components beyond the initially vulnerable plugin, potentially impacting the broader WordPress site. No known exploits are currently in the wild, and no patches have been officially released at the time of publication. The vulnerability is classified under CWE-79, which covers improper neutralization of input during web page generation leading to XSS. This vulnerability is significant because WordPress is widely used, and plugins like StreamWeasels Twitch Integration are popular for embedding Twitch streams, making it a valuable target for attackers aiming to compromise websites or their visitors through persistent script injection.

Potential Impact

For European organizations, the impact of this vulnerability can be substantial, especially for those relying on WordPress sites with the StreamWeasels Twitch Integration plugin installed. Successful exploitation could lead to session hijacking, defacement, unauthorized actions performed on behalf of users, and potential data leakage. This is particularly critical for organizations handling sensitive user data or providing services through their websites. The persistent nature of stored XSS means that all visitors to the compromised pages are at risk, increasing the attack surface. Additionally, compromised websites can be used to distribute malware or conduct phishing campaigns targeting European users, undermining trust and potentially violating GDPR requirements related to data protection and breach notification. The requirement for contributor-level access means insider threats or compromised accounts could be leveraged to exploit this vulnerability, emphasizing the need for strict access controls. Although no known exploits are currently active, the medium severity and ease of exploitation suggest that attackers may develop exploits, increasing risk over time.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify the presence of the StreamWeasels Twitch Integration plugin and verify the version in use. Until an official patch is released, organizations should consider disabling or uninstalling the plugin to eliminate the attack vector. Implementing strict role-based access control to limit contributor-level privileges can reduce the risk of exploitation. Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting the 'data-uuid' attribute can provide temporary protection. Security teams should monitor logs for unusual activity indicative of XSS attempts or unauthorized script injections. Additionally, applying Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Regularly updating WordPress core, plugins, and themes is essential once patches become available. Finally, educating content contributors about safe input practices and monitoring user-generated content can help prevent exploitation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-18T15:11:07.629Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68884b63ad5a09ad008aed4a

Added to database: 7/29/2025, 4:17:39 AM

Last enriched: 7/29/2025, 4:33:01 AM

Last updated: 8/31/2025, 4:46:17 AM

Views: 23

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats