CVE-2025-7810
BaseFortify
Publication date: 2025-07-29
Last updated on: 2025-07-29
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpres | streamweasels_kick_integration | 1.1.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the StreamWeasels Kick Integration WordPress plugin (up to version 1.1.4) is a Stored Cross-Site Scripting (XSS) issue. It occurs because the plugin does not properly sanitize or escape user-supplied input in the 'data-uuid' attribute. Authenticated users with contributor-level access or higher can inject malicious scripts into pages, which then execute whenever any user views those pages.
How can this vulnerability impact me? :
This vulnerability can allow attackers with contributor-level access to inject arbitrary scripts into the website. These scripts can execute in the context of other users visiting the affected pages, potentially leading to session hijacking, defacement, or unauthorized actions performed on behalf of users. It can compromise the integrity and security of the website and its users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying pages where the 'data-uuid' attribute may contain injected scripts. Since the vulnerability is a Stored Cross-Site Scripting (XSS) triggered by authenticated users with contributor-level access or higher, you can audit the content of pages generated by the StreamWeasels Kick Integration plugin for suspicious script tags or unusual JavaScript code within the 'data-uuid' attribute. There are no specific commands provided in the resources, but general approaches include using web vulnerability scanners that detect stored XSS or manually inspecting the HTML source of pages using browser developer tools. Additionally, monitoring HTTP responses for unexpected script injections in the 'data-uuid' attribute can help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the StreamWeasels Kick Integration plugin to the latest version that includes the security fix for CVE-2025-7810. The fix, committed on 07/28/2025, upgrades the Freemius SDK and implements secure UUID generation and validation to prevent improper UUID handling and stored XSS attacks. Applying this update will address the insufficient input sanitization and output escaping issues. Until the update can be applied, restrict contributor-level and higher user access if possible, and monitor for suspicious activity related to the plugin. [1]